Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Christoph Anton Mitterer
On Wed, 2015-03-25 at 16:19 -0400, Chet Ramey wrote: > When you start bash, and source your .bashrc, the history comment character > is not set. You haven't set it in .bashrc, I assume Yes, I haven't. > Since that's not set, the lines beginning with > `#[digit]' are not recognized as timestamps a

Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Christoph Anton Mitterer
On Wed, 2015-03-25 at 16:21 -0400, Chet Ramey wrote: > https://lists.gnu.org/archive/html/bug-bash/2011-02/msg00042.html Maybe I've missed something but that thread basically just discussed the same issue without giving a solution, right? I understand you concerns about any format changes, that's

mapfile segfaults when unsetting array in callback

2015-03-25 Thread Geir Hauge
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/local/share

Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Chet Ramey
On 3/25/15 3:50 PM, Christoph Anton Mitterer wrote: > There is the lithist thingy, to preserve newlines in commands which I'd > quite like. > But it doesn't work obviously when [re-]storing [from/]to the history > file. > > Would it be possible to have e.g. another option, so that things work > l

Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Chet Ramey
On 3/25/15 3:02 PM, Christoph Anton Mitterer wrote: > On Wed, 2015-03-25 at 14:48 -0400, Chet Ramey wrote: >> The history file truncation code already skips lines that look like history >> timestamps. Look at history.c:history_truncate_file(). > Ah? Hmm was that only recently introduced? > I'm ha

Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Christoph Anton Mitterer
On Wed, 2015-03-25 at 15:09 -0400, Chet Ramey wrote: > > I'm having bash4.3 with patches up to including 33. And this time I > > looked whether Debian added any of it's goodness ;-) > I'll take a look. Thanks :) Speaking of feature-requests and history... There is the lithist thingy, to preserv

Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Chet Ramey
On 3/25/15 3:02 PM, Christoph Anton Mitterer wrote: > On Wed, 2015-03-25 at 14:48 -0400, Chet Ramey wrote: >> The history file truncation code already skips lines that look like history >> timestamps. Look at history.c:history_truncate_file(). > Ah? Hmm was that only recently introduced? Bash-3.

Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Christoph Anton Mitterer
On Wed, 2015-03-25 at 14:48 -0400, Chet Ramey wrote: > The history file truncation code already skips lines that look like history > timestamps. Look at history.c:history_truncate_file(). Ah? Hmm was that only recently introduced? I'm having bash4.3 with patches up to including 33. And this time

Re: feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Chet Ramey
On 3/25/15 2:07 PM, Christoph Anton Mitterer wrote: > Hey. > > When HISTTIMEFORMAT is used the history time comment lines are written > to HISTFILE. > Therefore, HISTFILESIZE is effectively only half as large. > > Would it be possible to simply not count the history time comment lines > when enfo

feature-request: don't count history time comment lines when in HISTFILESIZE

2015-03-25 Thread Christoph Anton Mitterer
Hey. When HISTTIMEFORMAT is used the history time comment lines are written to HISTFILE. Therefore, HISTFILESIZE is effectively only half as large. Would it be possible to simply not count the history time comment lines when enforcing HISTFILESIZE? Cheers, Chris.

Re: read -e deletes extra characters

2015-03-25 Thread Chet Ramey
On 3/24/15 12:19 PM, isabella parakiss wrote: > On 3/24/15, Chet Ramey wrote: >> There are a number of unjustified expectations here. The biggest is that >> readline can know about characters printed to the screen by another >> program. Readline expects to be able to use the entire line and that

Re: sr #108708: fix for output of 'alias' command

2015-03-25 Thread Eduardo A . Bustamante López
On Wed, Mar 25, 2015 at 10:17:49AM -0400, Chet Ramey wrote: > On 3/25/15 6:35 AM, Eduardo A. Bustamante López wrote: > > Original-Report: https://savannah.gnu.org/support/index.php?108708 > > Reporter: Pasha Bolokhov > > > > Alias produces non-reusable output: > > This is fixed on the devel branc

Re: sr #108708: fix for output of 'alias' command

2015-03-25 Thread Chet Ramey
On 3/25/15 6:35 AM, Eduardo A. Bustamante López wrote: > Original-Report: https://savannah.gnu.org/support/index.php?108708 > Reporter: Pasha Bolokhov > > Alias produces non-reusable output: This is fixed on the devel branch. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

sr #108708: fix for output of 'alias' command

2015-03-25 Thread Eduardo A . Bustamante López
Original-Report: https://savannah.gnu.org/support/index.php?108708 Reporter: Pasha Bolokhov Alias produces non-reusable output: dualbus@yaqui:~$ alias -- -x='echo x' dualbus@yaqui:~$ alias -p alias -x='echo x' alias ls='ls --color=auto' 'help alias' claims it's reusable: alias -p|grep reusable

sr #108732: named pipe leaks for systems not support DEV_FD

2015-03-25 Thread Eduardo A . Bustamante López
Original report here: https://savannah.gnu.org/support/index.php?108732 On systems without /dev/fd support, using procsub will generate a temporary file. In the case of bash -c 'cat <(echo yes)', the no-fork optimization will cause this to not clean up the created temporary file. Reproduced agai