mited
capacity for processing information and visual stimuli. Color helps us
categorize the instructional stimuli we are presented with."
Best Regards
Alex
On 9/14/20 3:52 PM, Chet Ramey wrote:
On 9/13/20 5:59 AM, A M wrote:
Hello, I would like to submit a feature request/suggestion on Bash. (I
Hello, I would like to submit a feature request/suggestion on Bash. (I
was told submitting to this mailing list was the right way to do it.)
Feature request: Enable possibility of colored stderr output.
It would be really neat to have functionality that stderr could be
output in a different
Hello, I would like to make a feature request/suggestion on Bash. (I was
told submitting to this mailing list was the right way to do it.)
Feature request: Enable reverse-search-history (C-r) to be case-insensitive.
Currently reverse-search-history is case-sensitive and cannot be changed
to
On 7/21/20 2:48 PM, Greg Wooledge wrote:
On Tue, Jul 21, 2020 at 10:55:06AM +0300, M. Nejat AYDIN wrote:
Also, shouldn't the tilde be expanded following
$ echo ~:
? The colon terminates tilde-prefix in an assignment, but there is no
assignment involved here.
Works for me.
unicorn
In https://bugzilla.opensuse.org/show_bug.cgi?id=1100488
we found that depending on the build machine, bash-4.4's bash.html would
contain the string Bahh instead of Bash
strcpy can cause corruption when working on overlapping strings
so we use memmove instead that handles this case correctly
---
In https://bugzilla.opensuse.org/show_bug.cgi?id=1100488
we found that depending on the build machine, bash-4.4's bash.html would
contain the string Bahh instead of Bash
strcpy can cause corruption when working on overlapping strings
so we use memmove instead that handles this case correctly
---
On 2017-10-15 20:53, Eduardo A. Bustamante López wrote:
> I have some questions:
>
> 1. Which specific versions of 4.3 and 4.4?
> 2. Did you compile bash from source? (if so, what did you use for CFLAGS and
> the configure script parameters? are you
>using bash's malloc or the system
in advance for your insights
Bernhard M.
[1]
https://github.com/g23guy/supportutils/blob/1e89b672d61ac6da5d8cf4a164b529693eab0cd9/bin/supportconfig#L304
Thanks for the pointer. I reported it there (
https://github.com/scop/bash-completion/issues/52 ).
After further investigation, the problem seems to be that when IFS is
set to '*', case *) doesn't get executed. Is this the intended
behavior?
For example:
IFS='*'; case "foo" in *) echo "got
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-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
On 9/9/2012 6:52 PM, John E. Malmberg wrote:
On 9/9/2012 7:52 PM, Gregory M. Turner wrote:
I'd be happy to iterate if folks have some good ideas as to how to
improve the implementation.
Don't forget that the file test operators also need to be able to find
the same binary files. Otherwise
e6206e337ac4577e4b83ceaac44241f48a2aec50
Author: Gregory M. Turner gmturner...@ameritech.net
Date: Sat Sep 8 22:05:06 2012 -0700
lib/glob: cygwin: match executables without .exe suffix
On cygwin we have the .exe-hack which is a feature that
attempts to make the Windowsy .exe suffix
command] [-X filterpat] [-P
prefix] [-S suffix] [word]
After -sr I pressed tab for auto-completion. The minus was a typo
that caused the error.
--
João M. S. Silva
:/sbin'
-DSYS_BASHRC='/etc/bash.bashrc' -DSYS_BASH_LOGOUT='/etc/bash.bash
_logout'
uname output: Linux baboun 3.2.8-1-ARCH #1 SMP PREEMPT Mon Feb 27 22:13:59 UTC
2012 i686 Intel(R) Pentium(R) M processor 2.00GHz GenuineIn
tel GNU/Linux
Machine Type: i686-pc-linux-gnu
Bash Version: 4.2
Patch Level
.
From 3e0dc8781417fe9b7ba665d1bc3b49fd884ba8b0 Mon Sep 17 00:00:00 2001
From: Bradley M. Kuhn bk...@ebb.org
Date: Sat, 25 Jun 2011 14:27:12 -0400
Subject: [PATCH] HISTTIMEFORMAT should not be set while running existing histexp.tests
If it is, the test output is not correct. This change unsets
I agree with Marcel's points about keeping a big bash history, although
I wasn't sure if discussing why users keep a big bash history was on
topic or not.
Marcel (Felix) Giannelia wrote at 13:16 (EDT) on Tuesday:
A .bash_history file going back years and years is still only a few
megs,
Jayesh Badwaik wrote at 03:18 (EDT) on Saturday:
Every now and then I want a command from one of the instances of bash
to be used in another instance. In that case, the history of bash is
not that useful since it is quiet linear in nature and does not store
history of all bash instances.
Chet Ramey wrote at 15:59 (EDT) on Thursday:
I think there should be a master branch, and a branch that includes
posted patches other than those that have been officially released.
Then other branches as needed to accommodate developers.
I think that could work fine; I'm happy to do my best
Chet Ramey wrote at 17:25 (EDT) on Wednesday:
I think this is a great idea. I've already contacted Bradley and
encouraged him to go ahead. I'd like to thank him publicly for his
offer.
Thanks, Chet! It was my pleasure to set this up. Thanks to Jari for
the original idea and the first
Michael Witten wrote at 02:34 (EDT):
Perhaps (and hopefully) Bradley meant that file moves were separated
from any other content changes that might otherwise have occurred
simultaneously.
I probably did this in some cases and not others. Anyway, what I've got
is clearly better than what's on
Chet Ramey wrote on 2009-11-02:
Jari Aalto was setting up a git repository of current and older bash
versions on savannah. I'll keep him up to date with public versions
of bash
Bob Proulx wrote on 2009-11-02:
It looks like it has just recently been partially implemented.
I wrote earlier this evening:
I humbly suggest that http://git.savannah.gnu.org/cgit/bash.git be
replaced with this repository above that I've created. The new
repository contains everything that the current Savannah one does, but I
put much more effort into making commits fine-grained,
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
Hi,
There is an inconsistency between the man page and the texinfo page
regarding continue and break. I've attached a patch that addresses this.
--- bash-3.2/doc/bash.1 2006-10-03 08:54:26.0 -0400
+++ bash-3.2/doc/bash.1.liketexi 2008-05-16 17:17:11.0 -0400
@@ -6086,10 +6086,9
NOTICE:
All information in and attached to the e-mail(s) below may be proprietary,
confidential, privileged and otherwise protected from improper or erroneous
disclosure. If you are not the sender's intended recipient, you are not
authorized to intercept, read, print, retain, copy, forward,
25 matches
Mail list logo
