Timeline for Preserve bash history in multiple terminal windows
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2012 at 17:58 | history | post merged (destination) | |||
| Sep 13, 2012 at 22:14 | history | migrated | from stackoverflow.com (revisions) | ||
| Aug 18, 2012 at 6:14 | comment | added | weynhamz | @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, 2012 at 12:21 | comment | added | pts | @TechliveZheng: Would you share your simple and better solution with us, so we all can learn from it? (If so, please add an answer to the question.) | |
| Aug 17, 2012 at 9:33 | comment | added | weynhamz | Okay, thank you. I have come up with a much simple and better sulotion. | |
| Aug 15, 2012 at 10:45 | comment | added | pts | @Techlive Zheng: 1. The original .bash_history is deliberately not supported, because .merged_bash_history uses a different file format, so in case .merged_bash_history fails to load properly, bash won't accidentally clobber the accumulated history. Robustness by design, will be kept as is. 2. A github repo is a good idea in general, but I don't have time to maintain that for this project, so I'm not doing it. -- Yes, it conflicts with bashdb, and there is no easy solution (they use the same hooks). I'm not planning to work on a fix, but I'm accepting patches. | |
| Aug 15, 2012 at 10:28 | comment | added | weynhamz | 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, 2012 at 10:23 | comment | added | weynhamz | 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. | |
| Mar 25, 2011 at 17:40 | history | answered | pts | CC BY-SA 2.5 |