network profile
| bio | website | techlive.me |
|---|---|---|
| location | Ningbo, China | |
| age | 25 | |
| visits | member for | 1 year, 5 months |
| seen | Apr 18 at 9:41 | |
| stats | profile views | 4 |
|
Dec 16 |
comment |
Why does my system show only 3.2 GiB of RAM when I definitely have 4.0 GiB I suppose all your GB should be GiB? |
|
Oct 7 |
revised |
How to exit bash history search mode? Improve and format the answer. |
|
Oct 7 |
suggested | suggested edit on How to exit bash history search mode? |
|
Oct 5 |
revised |
Indirect return of all elements in an array Improve the answer |
|
Oct 4 |
revised |
Indirect return of all elements in an array Improve comments |
|
Oct 3 |
awarded | Supporter |
|
Oct 3 |
revised |
Indirect return of all elements in an array fix typo |
|
Oct 2 |
awarded | Teacher |
|
Oct 2 |
awarded | Editor |
|
Oct 2 |
revised |
Indirect return of all elements in an array added 40 characters in body |
|
Oct 2 |
answered | Indirect return of all elements in an array |
|
Aug 18 |
comment |
Preserve bash history in multiple terminal windows @psts, It turns out that it is not your script incompatible with bashdb. When shopt -s extdebug is set or bash --debugger is invoked in an interactive mode, the bashdb always complaines about the 'null filename' issue. It seems shopt -s extdebug and bash --debugger are not supposed to be run in interacive mode. Unfortunately, they don't handle this situation well. |
|
Aug 17 |
comment |
Preserve bash history in multiple terminal windows Okay, thank you. I have come up with a much simple and better sulotion. |
|
Aug 15 |
comment |
Preserve bash history in multiple terminal windows It seems the debug hook is conflicted with bashdb, the follow output every time I start a bash session. ``` bash debugger, bashdb, release 4.2-0.8 Copyright 2002, 2003, 2004, 2006, 2007, 2008, 2009, 2010, 2011 Rocky Bernstein This is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. ** Internal debug error _Dbg_is_file(): file argument null bash: _Dbg_filenames[$fullname]: bad array subscript ``` |
|
Aug 15 |
comment |
Preserve bash history in multiple terminal windows This is a nice solution, but I got a few questions though. 1. Can I use the original .bash_history file, I do not want another bash history file existed in my $HOME 2. May be you should consider set a github repo for this. |
