On 8/20/15 8:38 PM, Linda Walsh wrote:
>
>
> Chet Ramey wrote:
>>> The earlier spec had -e only exit a script if a *simple* (external)
>>> command failed. It didn't include builtins nor functions.
>>
>> This is not; builtins and functions are simple commands.
> ---
> The builtins are _complex_ b
On 8/19/15 2:48 AM, jtmoon+bash...@extrahop.com wrote:
> Fix:
> For some reason the RETURN traps are not being stacked. Instead, the
> current RETURN trap is just overwritten.
There is only a single RETURN trap. Functions do not have local traps. If
a return trap is set when a func
Hi I ran bashbug on the command line and entered all the information for my
bug report but then when I tried to submit it I got the following error:
$ jmarbas@jmarbas-System:~/linux/quiz$ bashbug
Send bug report to bug-bash@gnu.org,b...@packages.debian.org? [y/n] y
/usr/bin/bashbug: 267: /usr/bin/
Jerry Marbas writes:
> I use the manpage of bash a lot and when I want to find a command I usually
> type: \[
> But for 'read' entry has two spaces between 'read' and the '[' making me
> type: read \[
Try searching for '^ {7}read ' instead. There are commands that aren't
followed by opt
On 08/20/2015 04:19 PM, Jeff Bai wrote:
> Hello, and here is a patch set for both zh_CN and zh_TW localization update.
> I will send a separate message for bash 4.4.
Thanks, but please don't. Spamming the wrong list with 600k of
information that the majority of list readers can't read is
inapprop
On 8/20/15 7:19 PM, Jeff Bai wrote:
> Hello, and here is a patch set for both zh_CN and zh_TW localization update.
> I will send a separate message for bash 4.4.
Please use the GNU Translation project as the clearinghouse for translation
files.
http://translationproject.org/domain/bash.html
I be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/21/15 10:06 AM, Eric Blake wrote:
> GNU Coding Standards recommend that '$program --help' should list the
> preferred bug-reporting address, and that the corresponding .po file
> should then expand that information to ALSO list the preferred addr
On jue, 20-08-2015 a las 17:38 -0700, Linda Walsh wrote:
> Functions are a collection of many commands. They are not a single,
> simple statement. I remember using their return value in some cases.
>
> With the change, I couldn't run a func and have it return the
> value in $? (1 byte, I know) -
On Andreas Schwab wrote:
> Try searching for '^ {7}read ' instead. There are commands that
> aren't followed by options in the description.
entering «/^ *read⤶» may be easier to type (and remember)
Ángel González writes:
> entering «/^ *read⤶» may be easier to type (and remember)
It won't match, though.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
> >> On 11 Jun 2015 18:10, Thomas Wolff wrote:
> >> > as opposed to having a fancy colored prompt, I would like to be
> >> able to
> >> > set up coloring of the whole bash command input line (but not the
> >> > following command output). This could be achieved by adding a variable
> >> > like "AFT
On 08/21/2015 08:22 AM, Chet Ramey wrote:
> On 8/21/15 10:06 AM, Eric Blake wrote:
>
>> GNU Coding Standards recommend that '$program --help' should list the
>> preferred bug-reporting address, and that the corresponding .po file
>> should then expand that information to ALSO list the preferred ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/21/15 2:45 PM, Eric Blake wrote:
> On 08/21/2015 08:22 AM, Chet Ramey wrote:
>> On 8/21/15 10:06 AM, Eric Blake wrote:
>>
>>> GNU Coding Standards recommend that '$program --help' should list the
>>> preferred bug-reporting address, and that the c
On 08/21/2015 11:58 AM, Chet Ramey wrote:
>>> Bash bugs should be reported using `bashbug'. That's why it's listed
>>> in the help output.
>
>> Where?
>
> Run bash --help to get it, like the coding standards say.
I did.
> $ ./bash --help
> GNU bash, version 4.3.42(28)-release-(x86_64-apple-da
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' -DCO$
uname output: Linux cl 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29
11:21:34 UTC 2015 x86_64
Andreas Schwab wrote:
> Ángel González writes:
> > entering «/^ *read⤶» may be easier to type (and remember)
>
> It won't match, though.
It matches fine for me. Although I suggest adding the square bracket
so as to avoid the other false positives as long as one knows that
read has options docum
16 matches
Mail list logo
