ot;\" escape inside of single quotes, you would end up
with something more convoluted, like:
$ x='foo "foo" and '"'"'bar'"'"' content'
$ echo "$x"
foo "foo" and 'bar' content
Alternatively:
$ x='foo "foo" and '"'bar' content"
$ echo "$x"
foo "foo" and 'bar' content
Eric
BASHPID; f() { echo Function: $BASHPID; }; f
Parent: 2484818
Function: 2484818
~$ echo Parent: $BASHPID; f() ( echo Function: $BASHPID ); f
Parent: 2484818
Function: 2493192
Eric
that you might get in trouble for **not**
addressing someone with a title. Some of my older relatives will even
address me as Mr. [...] or Mister [...] when sending me physical
letters.
Eric
"Dale R. Worley" wrote:
> A priori, it isn't surprising. But the question becomes "What
> algorithmic improvement to bash would make this work faster?" and then
> "Who will write this code?"
I'll try to take a look at it in a few months if I run out of
things to do and nobody beats me to it. I'
Hi, I noticed bash struggles with gigantic completion lists
(100k items of ~70 chars each)
It's reproducible with both LANG+LC_ALL set to en_US.UTF-8 and C,
so it's not just locales slowing things down.
This happens on the up-to-date `devel' branch
(commit 584a2b4c9e11bd713030916d9d832602891733d7
65 MiB/s, done.
Resolving deltas: 100% (36225/36225), done.
$ cd bash/doc/
doc$ fgrep -r pretty
texinfo.tex:% above. But it's pretty close.
texinfo.tex: % and a tt hyphen is pretty tiny. @code also disables ?` !`.
doc$
Eric
On Fri, Nov 10, 2023 at 01:22:54PM -0500, Greg Wooledge wrote:
> It most definitely is *not* everywhere. It's part of GNU coreutils,
> and is generally not present on any system that does't use those (BSDs
> and commercial Unixes for example).
>From _seq(1)_ on FreeBSD:
> The seq command first a
On Thu, Sep 07, 2023 at 02:42:16PM +0700, Robert Elz wrote:
> Date:Wed, 6 Sep 2023 11:32:32 -0500
> From: Eric Blake
> Message-ID:
>
>
> | You (anyone reading this, not just kre) are welcome to join tomorrow's
> | Austin Group meetin
er (useful) conversion specifier in C. And given that, I prefer
naming such an extension option -C or -c (implying C-like), rather
than your suggestion of -b (implying binary, but where the implication
only benefits %b) as a better option name for such a printf extension
option.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
r than what existing practice has. Coreutils is
willing to do it, but I have not actually committed that patch yet,
waiting to see how this thread pans out.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
to mean "interpret my format string according
to C23 semantics" is also a viable idea, but one not mentioned in the
current incantation of the Austin Group bug. But that's why the bug
has a 30-day review period, to collect feedback comments on how it can
be better worded before Issue 8 is finalized.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
g that if
implementations are willing to implement it now, it will make Issue 9
easier to reason about.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Fri, Sep 01, 2023 at 08:59:19AM +0100, Stephane Chazelas wrote:
> 2023-08-31 15:02:22 -0500, Eric Blake via austin-group-l at The Open Group:
> [...]
> > The current POSIX says that %b was added so that on a non-XSI
> > system, you could do:
> >
> >
On Thu, Aug 31, 2023 at 04:01:17PM -0500, Rob Landley wrote:
> On 8/31/23 13:31, Eric Blake wrote:
> > POSIX Issue 8 will be obsoleting %b (escape sequence interpolation) so
> > that future Issue 9 can change to having %b (binary literal output)
> > that aligns with C2x.
>
On Thu, Aug 31, 2023 at 03:10:58PM -0400, Chet Ramey wrote:
> On 8/31/23 11:35 AM, Eric Blake wrote:
> > In today's Austin Group call, we discussed the fact that printf(1) has
> > mandated behavior for %b (escape sequence processing similar to XSI
> > echo) that will even
ynonym for %b is
probably going to be easier (less shell escaping needed). Is there
any interest in a patch to coreutils or bash that would add such a
synonym, to make it easier to leave that functionality in place for
POSIX Issue 9 even when %b is repurposed to align with C2x?
--
Eric Blake, Pr
From: Eric Li
To: bug-bash@gnu.org
Subject: Integer overflow of i in string_extract_verbatim
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -Og
uname output: Linux fedora 6.2.12-200.fc37.x86_64 #1 SMP
x55d3099d69d0 /*
72 vars */) = 0
/home/eblake
[pid 1248831] +++ exited with 0 +++
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1248831,
si_uid=14986, si_status=0, si_utime=0, si_stime=0} ---
+++ exited with 0 +++
According to POSIX, perl should REALLY be passing a "--" argument
between "-c" and the scalar string given by the user; see
https://www.austingroupbugs.net/view.php?id=1440
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On 3/30/21 3:44 PM, Chet Ramey wrote:
Is this a serious piece of code, or just one to demonstrate a programming
error?
The latter
There is only one field, terminated by `|', which becomes one array
element. This is where you `lose' the null elements, not when you attempt
to copy. Nothing you d
On 3/30/21 10:54 AM, Chet Ramey wrote:
> On 3/29/21 6:40 PM, Eric Cook wrote:
>> Its just when populating that array dynamically with another array
>> if that second array didn't contain `v1' hypothetically, the array gets
>> shifted to
>
> OK, how would you
On 3/29/21 5:18 PM, Chet Ramey wrote:
If you look at
a=( k1 v1 k2 v2 k3 v3)
as more or less syntactic sugar for
a=( [k1]=v1 [k2]=v2 [k3]=v3 )
it's reasonable that
a=( k1 v1 k2 )
is equivalent to
a=( [k1]=v1 [k2]= ). And that's what bash does.
Its just when populating that array dynamic
On 3/28/21 7:02 AM, Oğuz wrote:
As it should be. `[bar]' doesn't qualify as an assignment without an equals
sign, the shell thinks you're mixing two forms of associative array assignment
there.
In the new form, that a key is listed inside a compound assignment alone
implies that it was meant
On 3/28/21 12:25 AM, Oğuz wrote:
Why? I think it's better this way.
--
Oğuz
1) For consistency sake with the shell the idea was borrowed from mostly.
2) Prior to this extension bash required specifying the key and value for
AA assignments, so it seems weird to silently ignore that a value w
Hey,
When doing an assignment with an uneven number of elements bash currently
silently treat the last element
as a key and assigns it an empty string.
$ typeset -A ary=(this feature came from zsh); typeset -p ary
declare -A ary=([came]="from" [this]="feature" [zsh]="" )
In zsh this is an erro
rawback of not having these in the repo and not in .gitignore
>> is that a 'git status' complains about untracked files.
>
> OK, this is a good reason.
But even if the upstream repo doesn't want to ignore a file in the
(checked-in) .gitignore, you can always edit your (local-
ally set it; whereas using
printf is reliably portable.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
ined.
echo -- "-n foo" # -- -n foo
Also well-defined.
I see nothing in your report about bash disobeying POSIX, but rather
confusion on your part about what POSIX actually requires.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
On 8/16/20 11:47 AM, Todd A. Jacobs wrote:
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin19.5.0
Compiler: clang
Compilation CFLAGS: -DSSH_SOURCE_BASHRC -Wno-parentheses -Wno-format-security
uname output: Darwin titan.local 19.6.0 Darwin Kernel Versi
...
~$ bash -c 'echo ~nosuchuser'
~nosuchuser
glibc:
bash-5.0$ ldd --version
ldd (Debian GLIBC 2.28-10) 2.28
...
bash-5.0$ ./bash --version
GNU bash, version 5.0.17(2)-release (x86_64-pc-linux-gnu)
...
bash-5.0$ ./bash -c 'echo ~nosuchuser'
~nosuchuser
Eric
4.23(1)-release (x86_64-pc-linux-gnu)
GNU bash, version 5.0.16(1)-maint (x86_64-pc-linux-gnu)
I haven't looked up to see what POSIX has to say about this, but I'm fairly
confident that this flies in the face of it. If that's the case and this patch
is dismissed accordingly,
On 3/13/20 2:22 PM, Zack Weinberg wrote:
On Fri, Mar 13, 2020 at 3:13 PM Eric Blake wrote:
Unpatched bash 5.0 has a bug where calling $as_echo that contains \ can
result in unintended globbing, where the behavior of the expansion is
dependent on the contents of the current directory. Nasty
sions like that,
when it is already more efficient to use other means of iteration that
do not require bash to keep the entire sequence in memory.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
bout
its calling context and is complaining that it can't write a directory
atomically.
Not bash's problem. Carry on!
--
http://www.catb.org/~esr/";>Eric S. Raymond
devs are too busy for this like the idea, I could write
the patch.
--
http://www.catb.org/~esr/";>Eric S. Raymond
During waves of terror attacks, Israel's national police chief will
call on all concealed-handgun permit holders to make sure they carry
firearms at a
efore any of the POSIX word expansions, and is logically a separate step.
Then that argues that {Z..a} should produce \\ and \', rather than bare
characters, so that the subsequent quote removal gets back to the
intended character.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
from the unquoted backslash.
Yes - sure. But then I'm wondering why the unquoted backtick doesn't
start command substitution:
It may be version dependent:
$ echo ${BASH_VERSINFO[@]}
5 0 7 1 release x86_64-redhat-linux-gnu
$ echo b{Z..a}d
bash: bad substitution: no closing "`"
Just because Linux does not split whitespace on #! lines does not mean
that all operating systems behave the same. Mention the recent
coreutils 8.30 'env -S' addition for working around interpreter
argument limitations, as well as the use of env to locate bash even
when it is not in /bin.
---
do
#x27; to output exactly '-x', by virtue
of the fact that it mandates all utilities (other than special builtins)
with the specification 'OPTIONS None.' to parse and ignore '--' as the
end of options, whether or not the utility takes options as an
extension. If NetBSD broke t
Bash happens to have extension options, so your command
line is not portable, and it is not a bug in bash.
> Please, let's try to avoid losing control of printf like what
> happened to echo, stick to the requirements of POSIX where they
> apply and actually sp
on allows
an easy distinction between normal exit with 8-bit status and exit due
to signal.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
handlers for SEGV operating sanely when there is not
stack overflow. So in the meantime, the core dump is the best you'll get.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
e are confused
by the locale-specific nature of ranges otherwise).
>
> Repeat-By:
> foo=ABC ; echo ${foo%[A-Z]} ${foo%[:upper:]}
If you want [[:upper:]] to work, you have to spell it correctly.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualizati
ght be interrupting the window between open() and fcntl().
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
nefits
> of more lenient syntax. What are your thoughts?
Bad idea. Existing scripts can do:
echo = hi
and your proposal would change the semantics of that line from
outputting the string "= hi" to instead assigning to the variable named
$echo.
--
Eric Blake, Principal Software Engine
rates. The above quotes from POSIX demonstrate
ambiguous situations where lexical analysis, rather than parsing alone,
is needed to decide between arithmetic or command substitution; so since
we are already relegated to a lexical decision, complicating the parser
isn't going to buy us any benefit.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
html#tag_18_10
may be a helpful read for rules on deciding whether a TOKEN is further
resolved into reserved word or a plain WORD (although remember that
bash's parser recognizes more things than are required by the POSIX grammar)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
f unknown
lengths, the cache at least lets us avoid even more malloc()s of the
fixed-size management data structures.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
On 2/6/19 5:05 PM, Peng Yu wrote:
> On Wed, Feb 6, 2019 at 4:49 PM Eric Blake wrote:
>>
>> On 2/6/19 4:18 PM, Peng Yu wrote:
>>> Hi,
>>>
>>> I deleted the file parser-built, and bash still compiles and an empty
>>> parser-built file will be gen
ber]]...
So, the %left line that you quoted above IS what defined yacc_EOF to be
a token.
If you've never used yacc/bison before, trying to learn how they work by
using bash as your starting point is a rather heavy crash-course.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
ave you do all the work for me".
http://www.catb.org/esr/faqs/smart-questions.html is a great read; it
will teach you how to come across as someone worth chatting to, rather
than an infinite time sink, if you would use the advice in that file to
ask smarter questions.
--
Eric Blake, Principal Software E
For more details:
http://austingroupbugs.net/view.php?id=221
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
f distributed version control.
Nothing is preventing you from creating a github clone of the savannah
upstream git repository, and making your patches in whatever way you
prefer using github's processes; the only real leap is realizing that
you submit your patches as emails to this list rather than a
t.
If you think the existing convention is confusing, then submit a patch
to change it instead of asking someone else to take on the grunt work.
Otherwise, learn to live with the existing convention (which doesn't
bother me, so I won't be submitting a patch).
--
Eric Blake, P
On 11/15/18 12:00 PM, RAL wrote:
Hi,
How is defined the maximum number of characters a variable name can have?
Bash has no hardcoded limit, thus your maximum is dependent on how much
free memory your system has.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301
ause your /bin/sh is not bash, but probably
dash, and dash has picked a missing file as being treated as always an
error. That does not make it a bug in bash, though, but a difference in
behavior of your /bin/sh.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
o is to turn on the shift_verbose option in posix
mode.
Cool - I didn't realize we already had a shopt for that. Yes, it sounds
like in POSIX mode, shift_verbose should be turned on.
On a related note, should turning on POSIX mode also auto-enable xpg_echo?
--
Eric Blake, Principal Softw
On 11/9/18 8:52 AM, Chet Ramey wrote:
On 11/9/18 9:47 AM, Eric Blake wrote:
Well, there's STILL a conformance issue - the standard requires that unless
documented otherwise, any time a command line tool exits with non-zero
status, that it outputs a message to stderr explaining the
On 11/8/18 6:03 PM, Chet Ramey wrote:
On 11/8/18 3:37 PM, Eric Blake wrote:
If I'm reading POSIX correctly, shift is a special built-in utility, and if
'$#' is 0 or 1, then 'shift 2' counts as a utility error that shall exit
the shell, per the table in 2.8.1 Consequenc
r is greater than "$#", this may be
considered a syntax error and a non-interactive shell may exit; if the
shell does not exit in this case, a non-zero exit status shall be
returned. Otherwise, zero shall be returned.
Tested on Fedora 28 with bash-4.4.23-1.fc28.x86_64
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On Thu, Nov 24, 2016 at 12:05:20AM -0800, Eric Pruitt wrote:
> In my Bash configuration, I have things setup so Ctrl+Z is no longer
> translated into a signal at the Bash prompt so it can be remapped. Most
> recently, I decided to modify the Bash source to implement this change
On 09/06/2018 12:39 PM, Aharon Robbins wrote:
In article ,
Eric Blake wrote:
But bash could be taught to convert any regex that contains a range with
both endpoints ASCII into a different bracket expression before handing
things over to regcomp(). That is, if the user is matching against
[a
On 09/06/2018 09:17 AM, Chet Ramey wrote:
On 9/5/18 4:39 PM, Eric Blake wrote:
Or, you can use bash's 'shopt -s globasciiranges' which is
supposed to enable Rational Range Interpretation, where even in non-C
locales, a character range bounded by two ASCII characters takes
locale definition of only the ASCII characters in that range, rather
than the locale's definition of whatever other characters might also be
equivalent (actually, while I know that shopt affects globbing, I don't
know if it also affects regex matching - but if it doesn't, that's
probably a bug that should be fixed).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
other GNU utilities have done it for some
time. What do folks think?
I'm in favor of the idea.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
tml
https://cygwin.com/ml/cygwin/2018-05/msg00334.html
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
ssing operand
Try 'dirname --help' for more information.
$ dirname -- --
.
So, with that said, do you have an example command line that you are
still confused about, rather than a vague non-report?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
Makes no real difference to me on the Cygwin port. -p1 is slightly
nicer, but it's a scripted solution to apply patches, and very easy to
tweak the script to match whatever the patches look like.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtu
ignore-case' as
the two knobs used to fine-tune whether you are doing case-insensitive
completion, and if so, whether -/_ are part of that case-insensitivity.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On 05/24/2018 01:29 PM, Eric Blake wrote:
On 05/24/2018 01:18 PM, Chet Ramey wrote:
On 5/24/18 11:40 AM, gabriele balducci wrote:
hi
just tried to build/install readline-8.0-alpha and found the following
glitch:
Thanks for the report. I think a better fix is to not to attempt to
install
l the pieces that weren't installed the first time).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On 04/11/2018 10:57 AM, Chet Ramey wrote:
> Yep, that's an incompatibility. The `c.c' thing in the original report is
> just a red herring, though.
>
> Chet
>
If you are aiming for compatibility with zsh, the fact that `echo **' recurses
is also a bug.
o.
So back to the overall expression: if pipeline2 has non-zero status,
then pipeline3 is run, even though that is the echo statement you
incorrectly surmised would never display.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
se files aren't ever pushed to the bash git repositories (master,
devel).
If Chet doesn't want to patch the primary bash.git to ignore them for
everybody in .gitignore, you can still patch your downstream repo to
ignore them locally by instead adding those exclusions to .git/info/excl
On 01/02/2018 10:30 AM, Chet Ramey wrote:
> On 12/31/17 10:36 PM, Eric Cook wrote:
>
>> So to make my request more specific, i don't think the extglob !() should
>> match dotfiles when one of the patterns in the list is preceded with an
>> period.
>> to be mo
On 12/31/2017 01:47 PM, Chet Ramey wrote:
> On 12/29/17 6:55 PM, Eric Cook wrote:
>> When using an pattern that begin with an period in pattern-list, bash will
>> include dotfiles in the results.
>> This doesn't seem to be the case with the various korn shells that i ha
When using an pattern that begin with an period in pattern-list, bash will
include dotfiles in the results.
This doesn't seem to be the case with the various korn shells that i have seen.
Since extglob is based on
ksh's extension to globbing, this appears to be an bug.
$ shopt -s extglob; touch
doh - thanks - didn't think of that, and that makes more sense.
Nevermind then.
On 12/18/17 1:11 PM, DJ Mills wrote:
>
>
> On Mon, Dec 18, 2017 at 11:25 AM, Eric Engstrom <mailto:engst...@mtu.net>> wrote:
>
> Dear Bash Maintainer(s),
>
> Bash&#x
i
# Commented out, don't overwrite xterm -T "title" -n "icontitle" by
default.
# If this is an xterm set the title to user@host:dir
Thanks,
Eric
--
Eric Engstrom - engst...@mtu.net - PGP Key: 0xC440235DF11F74CF
$/='O'; eval ($_='print $_^pack"c25",');
__END__
58O7O26O26O84O65O74O48O42O24O4O17O75O114O6O64O89O2O68O93O39O42O49O51O52
ase on Scientific Linux 7 and it happens with the latest
> release on both.
Are you sure you tested correctly? test has always behaved differently
for one argument than for two.
At any rate, this is not a bug in bash, but more likely in your script.
--
Eric Blake, Principal Software Engineer
Re
have a new
output format specifically designed for reinterpretation in shell
(certainly 'env' and 'env -0' output is not designed for that). Maybe
adding 'env -p' (analagous to -p in various bash builtins) is a
worthwhile feature addition for upstream coreutils, but ag
ything unsafe. If you think you can make bash
gracefully handle ALL possible bad inputs WITHOUT exiting or going into
an infloop itself, then you are claiming that you have solved the
Halting Problem, which any good computer scientist already knows has
been proven to be undecidable.
--
Eric Blake,
uoted*glob"', are so gross that I can only point you to the web page
discussing how gross they are:
https://www.chiark.greenend.org.uk/~sgtatham/aliases.html
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
e posix standard.
Not just deprecated, but inherently ambiguous. There are situations
where you CANNOT tell whether the user meant -a to mean the binary
operator or a string being tested against, because POSIX (intentionally)
does not specify enough precedence rules in how to parse > 4 arguments.
thing. Of
> course, I give the copyright to the FSF.
Copyright assignment is more formal than that, if your patch is deemed
significant (small patches can be taken without assignment, but large
patches require actual paperwork and signatures, although these days
there are various countries wh
On 04/14/2017 11:33 PM, Steven Penny wrote:
> On Thu, 13 Apr 2017 13:48:04, Eric Blake wrote:
Sorry for my delay in noticing this.
>> Is it still a problem with pselect, where rebuilding with the same
>> configuration as 7.0.1-2 fixes things? I'm really not sure how to even
&
bug specifically mentions 'trap', and concludes that a
separate bug may need to be opened (which I could not find) giving the
same treatment to 'jobs'.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
o make all shells with
'local' to settle on a lowest common denominator).
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
it is easier to patch 'bash --posix' to use a shorter prompt than it
is to fix the POSIX wording, then that may be the course to take.
Also, the bash behavior of modifying PS4 during subshells does not match
what other shells do.
--
Eric Blake eblake redhat com+1-919-301-3266
Libv
ode without you being able to
prevent it. Shellshock was a case where bash could execute code before
your script began (hence a CVE), but infinite recursion is a case where
avoiding your script avoids the crash (therefore the bug is your script,
not bash, and not worth a CVE).
--
Eric Blake eb
trings using 'echo'. Use
'printf' instead. POSIX even tells you to do that.
> Please let us know if this a bug or do we have any other option to print
> -n ?
Not a bug.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvi
yntax.
'set -o pipefail' turns it on,
'set +o pipefail' turns it off
'set -o pipefail on' is the same as 'set -o pipefail; set on', which
turns it on but also changes $*.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
would be better implemented in C. Changing
VSUSP natively is also far faster than calling stty.
Eric
On Thu, Nov 24, 2016 at 12:05:20AM -0800, Eric Pruitt wrote:
> In my Bash configuration, I have things setup so Ctrl+Z is no longer
> translated into a signal at the Bash prompt so it can be remapped. Most
> recently, I decided to modify the Bash source to implement this change
en begin with a number?
Sadly, yes. In fact, username '0' need not have uid '0'.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
concept rather than a pull request. Please let me know what you
think.
Thanks,
Eric
--- eval.c 2016-06-02 15:49:27.0 -0700
+++ eval.c 2016-11-20 15:02:23.681680378 -0800
@@ -31,6 +31,7 @@
#include
#include
+#include
#include "bashintl.h"
@@ -69,6 +70,8 @@
int
reade
imply didn't know how
> to do that in an acceptable manner (within a loadable bash builtin). This
> should be done for other loadables as well (e.g. 'cat'). It would serve it's
> purpose as 'example' even better.
Yes, this I can agree with - having a GOOD e
y specifies the behavior of 'rm -f' without
arguments; with 'rm', you can do what you want (therefore you comply
with POSIX), but it's still nice to match what other implementations do.
While I think that it is neat that this builtin can be used to speed up
configure scripts, I don't think it is ready for prime time yet. It's
tough to recommend that autoconf be taught to use this sub-standard
implementation.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
Chet,
OK. No worries then. Thanks for the prompt reply and the clarification
regarding when isascii() is actually needed.
Regards,
Eric
On 10/10/2016 4:01 PM, Chet Ramey wrote:
On 10/7/16 12:54 PM, Eric W. Robertson wrote:
While building and testing GNU Bash 4.4 on OpenVMS, the GNU Bash
7)) == 0)
#else
# define IN_CTYPE_DOMAIN(c) isascii(c)
#endif
For platforms that do not implement the isascii() function the above
definition for the IN_CTYPE_DOMAIN() function macro is more likely to
produce correct behavior than its current definition in the Bash 4.4
release.
As always any additional wisdom and/or feedback that can be provided
regarding the above is greatly appreciated.
Thanks,
Eric
in testing the patch.
In the script where I ran into this problem, I simply suppressed the
warning using 2>&-, and that's what I will continue to do if I will
knowingly read files that contain null bytes.
Eric
1 - 100 of 698 matches
Mail list logo
