> Press Ctrl-u
OK I see this also works for
$ ^Rabcdefg^U
$ some command the boss told me to do
$ ^R^R
and voila! I am back to searching "abcdefg" again.
OK, I'll remember ^U. Case closed. Thanks everybody.
Hi Chet,
Thank you for your response.
But it does not make sense since sbrk failure will be checked:
mp = (union mhead *) sbrk (sbrk_amt);
/* Totally out of memory. */
if ((long)mp == -1)
goto morecore_done;
The script just runs when my equipment boots up. Also it is hard to reproduc
On 10/20/15 2:53 PM, Piotr Grzybowski wrote:
> hey,
>
> just out of curiosity, does this fix it (sorry I just finished when
> you wrote that it had been fixed):
Well, it does, but it's overkill on one hand and doesn't fix the underlying
problem on the other. What you want to avoid is truncating
hey,
just out of curiosity, does this fix it (sorry I just finished when
you wrote that it had been fixed):
diff --git a/bashhist.c b/bashhist.c
index d4c62e7..9b5cf5d 100644
--- a/bashhist.c
+++ b/bashhist.c
@@ -354,7 +354,7 @@ save_history ()
int r;
hf = get_string_value ("HISTFILE");
-
On 16 Oct 2015 11:37, Chet Ramey wrote:
> On 10/15/15 5:30 PM, Mike Frysinger wrote:
> >>> the bash compat feature seems to address this nicely: our standard says
> >>> we should use bash-3.2, so we set the compat level to that, and then we
> >>> have much stronger confidence in newer versions not
On 10/20/15 11:03 AM, Marko Teiste wrote:
> Description:
> setting HISTFILE=/dev/null and HISTSIZE=0 will replace /dev/null
> with regular file on exit (when running as root).
>
> Repeat-By:
> start bash with root priviledges
> HISTFILE=/dev/null
> HISTSIZE=0
> exit
>
> Fix:
> Check if HISTFILE
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-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
On 10/20/15 10:21 AM, ziyunfei wrote:
> Quoting from the bash manual:
>
> "If IFS has a value other than the default, then sequences of the whitespace
> characters *space and tab* are ignored at the beginning and end of the word,
> as long as the whitespace character is in the value of IFS (an
Quoting from the bash manual:
"If IFS has a value other than the default, then sequences of the whitespace
characters *space and tab* are ignored at the beginning and end of the word, as
long as the whitespace character is in the value of IFS (an IFS whitespace
character)."
If this is true, t
On 10/20/15 2:31 AM, Raveh Neeman wrote:
> Hello,
>
>
> I get a compilation error during a build of bash 4.3.30 on MSYS, MinGW.
Try the attached patch.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS
Vascom writes:
> doc/builtins.0 | 2 +-
This is a generated file. You need to edit doc/bash.1.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On 10/20/15 6:00 AM, Vascom wrote:
> ---
> doc/builtins.0 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/builtins.0 b/doc/builtins.0
> index dcdc6c5..26b3580 100644
> --- a/doc/builtins.0
> +++ b/doc/builtins.0
> @@ -1592,7 +1592,7 @@ BBAASSHH BBUUIILLTTIIN
On 10/19/15 10:47 PM, Kai Wang X wrote:
> Dear,
>
>
>
> We have two products which are using bash 4.2 and 4.3 separately. They all
> meet bash crash issue. Please refer to the attached files.
>
> It is hard for me to understand the bash source code to find the root cause
> out.
It really look
---
doc/builtins.0 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/builtins.0 b/doc/builtins.0
index dcdc6c5..26b3580 100644
--- a/doc/builtins.0
+++ b/doc/builtins.0
@@ -1592,7 +1592,7 @@ BBAASSHH BBUUIILLTTIINN
CCOOMMMMAANNDDSS
function
Dear,
We have two products which are using bash 4.2 and 4.3 separately. They all meet
bash crash issue. Please refer to the attached files.
It is hard for me to understand the bash source code to find the root cause out.
Please let me know if you have or need more information.
Thank you very much
In the output of the 'help' command in any bash upto and including
4.4-beta, the possible arguments in most of the commands listed are
shown in lowercase, but for some they are in uppercase. Examples:
alias [-p] [name[=value] ... ]
break [n]
case WORD in [PATTERN [| PATTERN]...) COMMANDS ;
Hello,
I get a compilation error during a build of bash 4.3.30 on MSYS, MinGW.
Enclosed are logs of ./configure and make commands.
Could you fix it or advise a solution/workaround?
Rind Regards,
Raveh Neeman
Freelancer
Codeh Technologies, Yokneam, Israel
mob: +972-544-634-318
log.
17 matches
Mail list logo
