On Tue, Jul 5, 2022, at 8:09 PM, Yair Lenga wrote:
> My opinion is that we should be looking at the expected behavior - for
> a developer that want to implement ”strong” error handling: any error
> will break execution until explicitly handled. In the same spirit as
> the ‘try … catch’ that fro
On Tue, Jul 5, 2022, at 6:34 PM, Yair Lenga wrote:
> I probably did not described the intended behavior clearly. I believe
> both cases should behave identical under errfail. The loop will ‘break’
> on the first iteration (false when word = a). Same for the all looping
> commands. I believe this
On Tue, Jul 5, 2022, at 5:18 PM, Yair Lenga wrote:
> I’m not in front of my desktop, so I can not verify behavior, but here
> is my expectation - let me know if it make sense, in the context of the
> project goal - every unhandled failed statement should unwind execution
> up, until explicitly h
On Fri, Jul 1, 2022, at 4:07 AM, Vangelis Natsios wrote:
> When creating an alias containing a path ending with a non-latin (e.g.
> greek) directory name, a space character is appended to the end of the
> path, causing the alias to fail.
Not quite: Neither "paths" nor "non-Latin" characters are ne
On Tue, Jul 5, 2022, at 7:01 AM, Yair Lenga wrote:
> Below is the patch for the new 'errfail' option.
This doesn't apply cleanly to "devel". I assume you made it against
"master", which isn't the development branch -- "devel" is. Sorry
I forgot to mention that earlier.
--
vq
On Mon, Jul 4, 2022, at 3:55 PM, Yair Lenga wrote:
> I'm sorry - I misunderstood your original comments. I'll prepare the
> patched version (at least, I would like to add comments before
> publishing...) , and share it.
> Where/how can I post it ?
Send it to this list as an attachment [1] with a .
On Mon, Jul 4, 2022, at 2:33 PM, Yair Lenga wrote:
> Thanks for taking the time to review my post. I do not want to start a
> thread about the problems with ERREXIT.
Neither do I.
> Instead, I'm trying to advocate for
> a minimal solution.
>
> [...]
>
> Please take a look at the specific short ex
On Mon, Jul 4, 2022, at 8:20 AM, Yair Lenga wrote:
> I was able to change Bash source and build a version that supports the new
> option 'errfail' (following the 'pipefail' naming), which will do the
> "right" thing in many cases - including the above - 'foo' will return 1,
> and will NOT proceed t
On Mon, Jun 20, 2022, at 6:28 AM, n+b...@monade.li wrote:
> From: Naïm Favier
>
> Currently, typing `cmd flag1 flag2` (note the two spaces), navigating
> between the two spaces and hitting Tab produces
> `COMP_WORDS=(cmd flag1 flag2)` without inserting an empty word between
> flag1 and flag2.
>
>
On Fri, Jun 24, 2022, at 9:57 AM, Kerin Millar wrote:
> On Fri, 24 Jun 2022 13:53:07 +0200 (CEST)
> "Ing. Gerold Broser" via Bug reports for the GNU Bourne Again SHell
> wrote:
>
>> heredoc-error.sh:
>>
>> #!/bin/bash
>> sed -f - heredoc-error.sh <<-SCRIPT
>> ␣␣s/something/else/
>> ⭲ s/mor
On Fri, Jun 10, 2022, at 10:19 AM, Chet Ramey wrote:
> I didn't look at more than mailx, but the description there makes it clear
> that $EDITOR needs to expand to a command name. `more' has similar wording
> ("The name of the editor shall be taken from the environment variable
> EDITOR.") and talk
On Thu, Jun 9, 2022, at 8:37 PM, Luciano wrote:
> By the way, git seems to interpret the EDITOR variable in a way
> consistent with C-x C-e, while the pass program as I said seems to just
> execute $EDITOR, like fc. I wonder if POSIX leaves room for
> interpretation here.
It does, insofar as it
On Sun, Jun 5, 2022, at 9:31 PM, Namikaze Minato wrote:
> @everyone, please let me know if I need to do something else to
> actually report the bug or if this thread is enough.
This thread is enough.
--
vq
On Fri, May 20, 2022, at 7:01 PM, Lawrence Velázquez wrote:
> On Fri, May 20, 2022, at 2:06 PM, Therese Godefroy via RT wrote:
>> I'm going to tell him there is no guarantee that this can be changed.
>> For one thing, it would be difficult to find a letter that doesn't
&g
On Fri, May 20, 2022, at 2:06 PM, Therese Godefroy via RT wrote:
> I'm going to tell him there is no guarantee that this can be changed.
> For one thing, it would be difficult to find a letter that doesn't
> take an unwanted meaning when associated with "word".
Perhaps something like "num" or "fd"
On Thu, May 12, 2022, at 11:34 PM, flyingrhino wrote:
> Should the "else" condition after the: || run if the last command in
> the: && section exits non zero?
Yes. This behavior is not a bug; ''A && B || C'' is simply not
equivalent to ''if A then B; else C; fi''.
https://mywiki.wooledge.or
> On Apr 24, 2022, at 3:41 PM, Oğuz wrote:
>
> 24 Nisan 2022 Pazar tarihinde Ángel yazdı:
>>
>> I think a shopt makes more sense. Forcing heredocs to be files although
>> something legit to request, is more a caller workaround to bugs in
>> called programs.
>>
>
> https://lists.gnu.org/archiv
On Fri, Apr 22, 2022, at 9:51 AM, Sam Liddicott wrote:
> Fix:
> Please could we at least have a shopt to maintain the old behaviour?
Perhaps BASH_COMPAT=5.0 could be extended to handle this.
--
vq
On Sat, Apr 9, 2022, at 8:14 PM, Ayoub Misherghi wrote:
> Below I show two ways I ssh logged into a machine.
> In the first method I referred to the remote machine
> as 192.168.0.212 while in the second method I referred to the
> remote machine as [1]testuser5@192.168.0.212 specify
On Fri, Apr 8, 2022, at 3:23 PM, Chet Ramey wrote:
> So the difference is between a command not found
>
>> $ ./testfail1
>> a
>> ./testfail1: line 3: fail_command: command not found
>> b
>> $ ./testfail2
>> a
>> ./testfail2: line 3: 1 + : syntax error: operand expected (error token is
>> "+ ")
>> b
> On Mar 30, 2022, at 1:37 AM, Alex fxmbsw7 Ratchev wrote:
>
> your default of not allowing is weird
>
> seems 'allowing alias foreworders to speak' not good to you ?
You're misrepresenting what I said and what Chris said. Read
messages more closely before you pop off.
--
vq
> On Mar 29, 2022, at 8:26 AM, Chris Elvidge wrote:
>
> On 28/03/2022 22:00, Greg Wooledge wrote:
>> Or -- and I know this answer will be rejected, because it's too simple
>> and sensible -- stop using aliases in scripts.
>
> +1
>
> Or could just stop answering questions about aliases in script
On Mon, Mar 28, 2022, at 3:06 PM, Martin Schulte wrote:
> on Mon, 28 Mar 2022 20:34:40 +0200 Alex fxmbsw7 Ratchev
> wrote:
>> https://pastebin.com/raw/T7ZnFapt
>
> Here's a somewhat stripped down version:
>
> $ bash --noprofile --norc -i -c "echo \$BASH_VERSION; shopt -s
> expand_aliases ; sourc
On Tue, Mar 22, 2022, at 11:05 PM, L A Walsh wrote:
> On 2022/03/22 14:04, Lawrence Velázquez wrote:
>> On Tue, Mar 22, 2022, at 4:53 PM, L A Walsh wrote:
>>
>>> On 2022/03/21 03:40, Alex fxmbsw7 Ratchev wrote:
>>>
>>>> i solve this by shopt -s
On Tue, Mar 22, 2022, at 4:53 PM, L A Walsh wrote:
> On 2022/03/21 03:40, Alex fxmbsw7 Ratchev wrote:
>> i solve this by shopt -s nullglob
>>
>>>
>>> Repeat-By:
>>>Code: x=("/"); for i in "${x[@]%/}"; do echo "i is '$i'"; done
>>>Result: none
>>>Expected result: i is ''
>>>
> if
On Mon, Mar 21, 2022, at 8:50 AM, Alexey via Bug reports for the GNU Bourne
Again SHell wrote:
> I can add one more example, which change array size while it's not
> expected behavior:
> x=("/"); y=("${x[@]%/}"); echo "x size: ${#x[@]}, y size: ${#y[@]}"
This discrepancy seems to have been intro
On Wed, Feb 16, 2022, at 8:27 PM, Daniel Qian wrote:
> I'm not familiar with Bash version/release policy, I only found 5.1.8,
> 5.1.12, 5.1.16 at
> download page https://ftp.gnu.org/gnu/bash/
>
> Is this fix included in 5.1.16 version?
Yes, bash 5.1.16 is bash 5.1 with patch 16 and all previous of
On Mon, Feb 7, 2022, at 1:26 AM, Alex fxmbsw7 Ratchev wrote:
> well i saw now, printf a char of "\0" results in 0 bytes out to wc -c
% /usr/bin/printf '\0' | wc -c
1
> however my solution still stays
> you just use memory locations instead of c strings
> and those entries in memory are of
On Sun, Feb 6, 2022, at 11:53 PM, Alex fxmbsw7 Ratchev wrote:
> On Mon, Feb 7, 2022 at 12:02 AM Greg Wooledge wrote:
>> There are other programming languages besides bash. Some of them can
>> store NUL bytes internally, either by encoding and decoding them on the
>> fly, or by not using C-style s
> On Sat, Feb 5, 2022 at 9:46 PM Chet Ramey wrote:
>>
>> On 2/5/22 3:44 PM, Alex fxmbsw7 Ratchev wrote:
>> > maybe ask about an shopt feature to enable straight alias expansion
>> > when the aliases are following ..
>>
>> How would that, whatever it is, help you here?
I think he wants an option t
On Wed, Feb 2, 2022, at 9:30 AM, L A Walsh wrote:
> Instead of worrying about effects of dirnames on PS1, one might worry
> about how the directory names were created in the first place, and then
> worry about why one would deliberately 'cd' into such a directory.
https://en.wikipedia.org/wiki/Red
On Sat, Jan 22, 2022, at 6:10 PM, L A Walsh wrote:
> So I would ask which user-controlled prompts are "illegal" such that
> they would be sanitized?
I guess you're concerned with "(along with other user-controlled
substitutions in the prompt)". I'm not entirely sure what the OP
meant by that, an
On Fri, Jan 21, 2022, at 3:29 PM, Chet Ramey wrote:
> On 1/21/22 1:43 AM, Lawrence Velázquez wrote:
>
>> Personally, I would be
>> less than pleased if my whole terminal turned red just because I
>> changed into a directory that happened to have a weird name.
>
> A
On Sat, Jan 22, 2022, at 5:57 AM, Andreas Schwab wrote:
> On Jan 21 2022, Lawrence Velázquez wrote:
>
>> Depends what you consider to be an issue. Personally, I would be
>> less than pleased if my whole terminal turned red just because I
>> changed into a directory that
On Tue, Jan 18, 2022, at 9:13 PM, Josh Harcombe wrote:
> If a folder that is being displayed as part of the PS1 prompt contains
> escape sequences, bash will interpret them literally instead of escaping
> them like zsh does for example. Escape sequences should be fine if directly
> part of the prom
On Fri, Jan 21, 2022, at 12:22 AM, L A Walsh wrote:
> On 2022/01/18 22:31, Alex fxmbsw7 Ratchev wrote
>>> Fix:
>>> Haven't looked deeply into the bash internals but sanitizing the directory
>>> name (along with other user-controlled substitutions in the prompt) should
>>> work.
>>>
> Sanitizin
On Tue, Dec 21, 2021, at 10:48 PM, Dale R. Worley wrote:
> Lawrence Velázquez writes:
>> Did you mean to say that ${#FOO[*]} causes an error? Because
>> ${FOO[*]} does not, a la $*:
>
> The case that matters for me is the Bash that ships with "Oracle Linux".
On Tue, Dec 21, 2021, at 5:40 PM, fatiparty--- via Bug reports for the GNU
Bourne Again SHell wrote:
> Have tried to read some information about the format specifier for
> printf, particularly the width, precision and left justification for
> %s, but could not find any.
https://pubs.opengroup.o
On Thu, Dec 16, 2021, at 11:45 PM, Lawrence Velázquez wrote:
> Did you mean to say that ${#FOO[*]} causes an error? Because
> ${FOO[*]} does not, à la $*:
>
> [...]
>
> Like ${FOO[*]}, ${FOO[@]} and $@ are exempt from ''set -u''.
Perhaps you're using a
On Thu, Dec 16, 2021, at 11:01 PM, Dale R. Worley wrote:
> A bit ago I was debugging a failing script at work. It turns out that
> when you say
> FOO=(x y z)
> then the variable FOO is an array and is defined. But when you say
> FOO=()
> then the variable FOO is an array (because ${#FOO[*
On Sun, Dec 12, 2021, at 9:03 PM, Mallika wrote:
> I'm a little confused about how all the and's and or's combine (I suppose
> it's obvious if you're a little more familiar with the material - but it
> would be great if it were possible to express this by indentation),
It's a relatively confusing
On Tue, Nov 30, 2021, at 6:34 PM, Chet Ramey wrote:
> On 11/30/21 3:53 PM, Robert Swinford wrote:
>> (and globbing in zsh evals /*/* to //):
>
> Why? Under what circumstances is that correct?
I assume that OP is incorrectly describing zsh's default behavior
of intercepting risky ''rm'' commands an
On Sun, Nov 28, 2021, at 4:01 AM, Alex fxmbsw7 Ratchev wrote:
> printf 'e=. ; (( $# > 1 )) && $e afile "${@:1:$# -1}"' >afile ; . afile 1 2
> 3
>
> bash: : command not found
>
>
> 1. the cmd=. works out, no command error
> 2. on second+ run it shows this error, as bin/. is no command in $PATH
> 3.
On Tue, Nov 23, 2021, at 10:35 PM, Martijn Dekker wrote:
> Op 20-11-21 om 23:54 schreef Robert Elz:
>> What the devel one does is unknown to me, I don't think I even have
>> the means to obtain it (I have nothing at all git related, and no interest
>> in changing that state of affairs).
>
> Github
On Wed, Nov 17, 2021, at 7:35 AM, João Almeida Santos wrote:
> I’m a programming student currently on 42 School in Lisbon, and one of
> our projects is to create a minishell, and to mimic the behavior of
> bash.
Nice!
> While testing the heredoc mode, I realized that the $ is not
> interpreted
On Sun, Nov 14, 2021, at 11:40 AM, 積丹尼 Dan Jacobson wrote:
> Man page says:
>-vPrint shell input lines as they are read.
>-xPrint commands and their arguments as they are executed.
> Perhaps mention that -x and -vx give the same results, often or always.
They don't,
On Fri, Nov 12, 2021, at 4:36 AM, Mischa Baars wrote:
> Using Fedora 32 (bash 5.0.17) this returns a true, while on Fedora 35 (bash
> 5.1.8) this returns a false:
> touch test; if [[ -N test ]]; then echo true; else echo false; fi;
>
> [...]
>
> As I understand it, -N stands for NEW and therefore s
On Sat, Nov 6, 2021, at 2:41 AM, Alex fxmbsw7 Ratchev wrote:
> cat function/command_not_found_handle
> m "$BASH_COMMAND"
>
> type m
> m is aliased to `vim'
>
> type command_not_found_handle
> command_not_found_handle is a function
> command_not_found_handle ()
> {
> vim "$BASH_COMMAND"
> }
lma
On Sun, Oct 24, 2021, at 7:28 AM, Shehu Dikko wrote:
> Use this tldr client to get all the git tips you need and much else besides:
>
> https://github.com/raylee/tldr-sh-client
>
> tldr: https://tldr.sh
There's also #git on irc.libera.chat, if you prefer.
--
vq
On Fri, Oct 22, 2021, at 10:27 PM, Dennis Williamson wrote:
> I'm sure there are lists that provide git support.
Like this one.
https://groups.google.com/g/git-users
Or this one.
mailto:g...@vger.kernel.org
--
vq
On Wed, Oct 20, 2021, at 7:43 PM, Alex fxmbsw7 Ratchev wrote:
> to tell u honestly, im in no state to read freely happily new docs
I'll be honest as well: If you're not going to put in effort beyond
running commands that are spoon-fed to you, then I'm not going to
put in effort beyond dumping URLs
On Wed, Oct 20, 2021, at 5:07 PM, Alex fxmbsw7 Ratchev wrote:
> you got other cmd suggestions i can run to help debugging ? im very limited
> in bin.c debugging
You could bisect the devel branch to determine whether your problem
was caused by a change to bash and, if so, which commit is responsibl
On Sun, Sep 19, 2021, at 3:25 PM, 積丹尼 Dan Jacobson wrote:
> $ help for
> only mentions
>for name [ [ in [ word ... ] ] ; ] do list ; done
> and needs to be updated to mention
>for (( expr1 ; expr2 ; expr3 )) ; do list ; done
Not particularly intuitive, but:
bash-5.1$ help 'for (('
On Mon, Sep 6, 2021, at 6:46 PM, L A Walsh wrote:
> On 2021/09/05 20:54, Lawrence Velázquez wrote:
> > The distribution ships with a "realpath" loadable builtin, FWIW.
> >
>
> I didn't know that... um, my bash isn't quite there yet:
>
> I
On Sun, Sep 5, 2021, at 11:11 PM, Dale R. Worley wrote:
> L A Walsh writes:
> > I know how -h can detect a symlink, but I was wondering, is
> > there a way for bash to know where the symlink points (without
> > using an external program)?
>
> My understanding is that it has been convention to use
On Wed, Sep 1, 2021, at 8:20 PM, Ananth Chellappa wrote:
> I hope I can make a genuine contribution at some point.
If you're hoping/planning on getting these changes accepted into
bash, it might be worth hashing out details with Chet before expending
your time and energy. (I am not a contributor,
On Tue, Aug 31, 2021, at 4:02 AM, Lawrence Velázquez wrote:
> ksh does not blindly remove all leading whitespace
For the curious, this is how ksh(1) describes it:
If '#' is appended to '<<', then leading spaces and tabs
will be stripped off the firs
> On Aug 31, 2021, at 3:16 AM, Přemysl Šťastný wrote:
>
> I didn't realize yesterday, that ksh93 is not a nick name, but ksh version
> 93. :D
Sort of.
> So it would be okey with you, if I try to implement it using <<#?
The bash maintainer (who is not me) hasn’t yet indicated whether this is
On Mon, Aug 30, 2021, at 5:22 PM, Přemysl Šťastný wrote:
> Will ksh93 version ever get to upstream?
I don't know what you mean by that. ksh is not "downstream" of
bash; it is a separate project. Whether bash incorporates this
feature or one like it is up to Chet, who hasn't yet chimed in.
> Thi
On Mon, Aug 30, 2021, at 4:06 PM, Přemysl Šťastný wrote:
> I think, it would be nice, if you implemented Squiggly heredoc, which
> solves this problem by ignoring both leading spaces and leading tabs. eg.
>
> func()(
> cat <<~ EOF
> blabla
> EOF
> )
'<<~' is already syntactically vali
On Fri, Aug 27, 2021, at 1:20 PM, nigelberlinguer wrote:
> ‐‐‐ Original Message ‐‐‐
> On Friday, August 27, 2021 4:02 PM, Robert Elz wrote:
> > XBD 12.2 guideline 7 is:
> >
> > Guideline 7: Option-arguments should not be optional.
> >
> > That is, if you want to be able to give an option a
On Wed, Aug 25, 2021, at 5:18 AM, Dietmar Schindler wrote:
> > sent: 25. August 2021 02:14
> > from: "Lawrence Velázquez"
> > Cc: bug-bash@gnu.org
> > On Tue, Aug 24, 2021, at 4:44 PM, Dietmar P. Schindler wrote:
> > > Doesn't the example I
On Tue, Aug 24, 2021, at 4:44 PM, Dietmar P. Schindler wrote:
> Doesn't the example I gave above show that quotes are removed? If they
> weren't, how could word aa with pattern a""a constitute a match?
The quotes are handled by the matching process itself, *not* as
part of the usual shell expansio
> On Aug 22, 2021, at 10:22 PM, Koichi Murase wrote:
>
> 2021年8月23日(月) 6:13 Emanuele Torre :
>> It would be nice to have a parameter transformation (e.g. "${par@p}")
>> that expands $par to a string that will not be expanded by PS1, PS2, &c.
>
> It seems to me that you can just put '$par' (not "
On Sun, Aug 22, 2021, at 4:38 PM, Alex fxmbsw7 Ratchev wrote:
> last time again
You promise?
> one pair quotes, not more
Except you're wrong.
$ val=foo
$ declare "$val"='x'
$ declare -p "$val"
declare -- foo="x"
$ val=bar
$ declare -a "$val"='(baz quux)'
$ declare -p "$val"
declare -a bar=([0]
On Sat, Aug 21, 2021, at 6:02 PM, Hunter Wittenborn wrote:
> In my head, something like this (where 'value' is equal to 'y'):
>
> `declare "${value}"="x"`
>
> becomes this (which it appears to do so):
>
> `declare "y"="x"`
Almost. The argument parses without issue ('=' has no special
meaning h
> On Fri, Aug 20, 2021 at 10:30 PM hancooper via Bug reports for the GNU
> Bourne Again SHell bug-bash@gnu.org wrote:
>
> I am using EPOCHREALTIME and then computing the corresponding human
> readable form, that can handle
> changes in locale
> now=$EPOCHREALTIME
> printf -v second '%(%S)T.%s' "${
On Fri, Aug 20, 2021, at 6:11 PM, Léa Gris wrote:
> Le 21/08/2021 à 00:06, Chet Ramey écrivait :
> > The best way to clone an associative array is:
> >
> > declare -A options
> > eval options=\( "${assoc[@]@K}" \)
> >
> > The quoting @K performs is eval-safe.
> >
>
> Although I was not attempti
On Sat, Aug 14, 2021, at 7:56 PM, Keith Thompson wrote:
> Bash Version: 5.1
> Patch Level: 4
> Release Status: maint
>
> Description:
> The builtin "printf" command with the "-v" option works
> correctly, but it reports failure by setting $? to 1.
>
> The problem was intro
On Sat, Aug 14, 2021, at 6:59 PM, George Nachman wrote:
> Description:
> Defining an alias named `done` breaks parsing a for loop that does not have
> an `in word` clause.
>
>
> Repeat-By:
>
> Run the following script. It fails with this error:
>
> myscript.bash: line 7: syntax error near unexp
On Sat, Jul 31, 2021, at 4:17 PM, Jean-Jacques Brucker wrote:
> The advantage of adding such variable is that we could use more easily
> different mo files in a same bash execution :
>
> (at least) one "legacy" (for /$"..."/) and (at least) one 'C-strings'
> (for /$'...'/), which could then be s
> On Jul 13, 2021, at 4:37 PM, Paul Gilmartin wrote:
>
> Description:
> When "word" in here-document contains command substitution,
> bash reports an error:
> here: line 4: warning: here-document at line 2 delimited by end-of-file
> (wanted `foo$( true )bar')
> Man bash shows:
> On Jul 7, 2021, at 10:38 PM, lisa-as...@perso.be wrote:
>
> Correct. How do others customarily use `${fdir:=$PWD}` ?
The common idiom is
: "${fdir:=$PWD}"
The ':' utility is used because it does nothing, but its arguments
are expanded as usual.
> I'd rather understand what's going on, r
On Wed, Jul 7, 2021, at 6:37 PM, lisa-as...@perso.be wrote:
> So you used `:` at the beginning and it worked?
Chet and Greg already spelled out your mistake. It has nothing to
do with the ':' command.
--
vq
On Tue, Jun 29, 2021, at 4:38 PM, Jay K wrote:
> diff -u input_avail.c.orig input_avail.c
> --- input_avail.c.orig 2019-12-26 13:59:17.0 -0800
> +++ input_avail.c 2021-06-29 12:48:19.407119600 -0700
> @@ -110,7 +110,7 @@
> #if defined(HAVE_SELECT)
> fd_set readfds, exceptfds;
>
On Tue, Jun 22, 2021, at 8:52 PM, Martin Jambon wrote:
> It's better. However, the reader is still left wondering what "the
> shell" is referring to in first sentence.
Subshells aside, I have a hard time believing that "the process ID
of the shell" confuses anybody in practice. Even POSIX doesn'
On Tue, Jun 22, 2021, at 6:32 PM, Martin Jambon wrote:
> I would also mention pipelines here, since these are more commonly
> used than () subshells. I don't know if there are other ways of
> creating subshells. If that's all, I think it would be valuable
> to mention those two cases rather than
On Sun, Jun 6, 2021, at 12:35 AM, G. Branden Robinson wrote:
> At 2021-06-05T23:29:58-0400, Lawrence Velázquez wrote:
> > doc/oldbash.texi
> > 178:manual. Brian and Diane would like to thank Chet Ramey for his
> > 9138:# The alternative explanation is that hi
> On Jun 5, 2021, at 12:47 PM, John Passaro wrote:
>
> I can see a couple reasons why it would be a good thing, and in the con
> column only "I personally don't have time to go through the manual and make
> these changes".
There don't seem to be many instances in the Texinfo source.
#1, already
On Sat, May 15, 2021, at 4:29 PM, Alex fxmbsw7 Ratchev wrote:
> but is that the devel tree
Switch to the "devel" branch.
--
vq
> On Apr 19, 2021, at 7:18 AM, Greg Wooledge wrote:
>
> On Mon, Apr 19, 2021 at 01:16:48AM -0400, Grisha Levit wrote:
>> I think you can do something similar to the patch directly in the shell by
>> temporarily unsetting HISTFILE and then deleting history entries in a
>> certain range and restori
> On Apr 18, 2021, at 7:12 PM, Ananth Chellappa wrote:
>
> Even this guy https://paulh.consulting/
> thought it was easy before deciding it was worth $500 of his time to try
> adding it :)
I don't know who "this guy" is. There are a lot of very skilled
developers who aren't specifically versed
Hi,
> On Apr 18, 2021, at 12:03 AM, Ananth Chellappa wrote:
>
> Hello Brian and Chet,
> Please consider merging the enhancement made by Naseeba described
> here :
>
> https://github.com/ananthchellappa/bash-5.1/blob/main/README.md
In your future emails, you may want to consider
- writ
On Fri, Apr 9, 2021, at 4:51 PM, Eli Schwartz wrote:
> Are you ready to have your day truly spoiled? Fedora's package for the
> external program GNU which, provides this /etc/profile.d/ script
> (automatically injected into the environment of any interactive shell
> sessions once you install GNU wh
On Tue, Mar 30, 2021, at 4:50 PM, Greg Wooledge wrote:
> On Wed, Mar 31, 2021 at 02:31:46AM +0700, by.sm--- via Bug reports for
> the GNU Bourne Again SHell wrote:
> > poc=whoami
> > $poc
> > python3 -c "print('!!')"
> >
> > That return 'whoami' command.
>
> You're running into the csh-style hi
On Tue, Mar 30, 2021, at 12:54 PM, L A Walsh wrote:
> On 2021/03/29 20:04, Greg Wooledge wrote:
> > On Mon, Mar 29, 2021 at 07:25:53PM -0700, L A Walsh wrote:
> >
> >>
> >>I have both /etc/profile and /etc/bashrc call my configuration
> >> scripts. Are there common paths that don't call one
> On Mar 24, 2021, at 5:21 PM, gregrwm wrote:
>
> Oddly, somehow, invoking ssh in a loop causes the loop to preterminate.
> Why?
https://mywiki.wooledge.org/BashFAQ/089
vq
> On Mar 23, 2021, at 11:43 PM, Eli Schwartz wrote:
>
> On 3/23/21 11:24 PM, L A Walsh wrote:
>> Too often I end up having to write something like
>> if (($#)); then "$@"
>> else # = function or executable call
>> fi
>>
>> It would be nice to have a expansion that preserves arg boundaries
> On Mar 16, 2021, at 11:08 PM, Dennis Williamson
> wrote:
>
> I've been playing with your optimized code changing the read to grab data
> in chunks like some of the other optimized code does - thus extending your
> move from by-word to by-line reading to reading a specified larger number
> of c
> On Mar 16, 2021, at 6:01 PM, Jay via Bug reports for the GNU Bourne Again
> SHell wrote:
>
> Hello,
>
> I have been using/exploring Linux for ~ 2yrs; have corrupted a couple
> systems more than once either through their instability with libraries
> or just excess stress.
>
> I don'
> On Mar 15, 2021, at 9:03 PM, Léa Gris wrote:
>
> Please excuse my profanity of mentioning zsh in this list, but I really think
> features and behavior convergence can benefit end users in multiple ways,
> especially when expanding beyond the POSIX sh scope.
>
> What direction has taken zsh w
> On Feb 17, 2021, at 10:27 PM, Dale R. Worley wrote:
>
> Lawrence Velázquez writes:
>>>> `;;' is optional for the last case item.
>>>
>>> The manual page (for my version) says it's required. If, in some
>>> certain circumstances, i
> On Feb 16, 2021, at 10:42 PM, Dale R. Worley wrote:
>
>> Oğuz writes:
>>
>> `;;' is optional for the last case item.
>
> The manual page (for my version) says it's required. If, in some
> certain circumstances, it works without, that's nice.
It's also required by POSIX.
> But there's no c
> On Feb 15, 2021, at 10:01 AM, Chet Ramey wrote:
>
> The bash command substitution parser handles the majority of these
> cases (heh)
lol I chuckled, well done
vq
> On Feb 14, 2021, at 3:00 PM, Oğuz wrote:
>
> 14 Şubat 2021 Pazar tarihinde Dale R. Worley yazdı:
>
>> Before we worry about what to change, I want to note that the original
>> example is syntactically incorrect. The example is
>>
>> $ bash -c ': $(case x in x) esac)'
>>
>> But the manual
> On Feb 13, 2021, at 5:21 PM, Robert Elz wrote:
>
> This problem has been known for a LONG time, without it being fixed.
I played around with shbot on Freenode for a bit. "LONG time" is right:
bash50 -c ': $(case x in x) esac)'
bash50: -c: line 0: unexpected EOF while looking for matching `
> On Sat, Feb 13, 2021, 21:34 Alex fxmbsw7 Ratchev wrote:
>
> you didnt end the case, wrong syntax
> echo $( case x in y) printf 1 ;; x) printf 2 ;; esac )
$ case x in x) esac
$ echo $?
0
> On Feb 13, 2021, at 3:36 PM, Alex fxmbsw7 Ratchev wrote:
>
> you have to specify something for ) even w
> On Feb 8, 2021, at 5:29 PM, gregrwm wrote:
>
> $ export vim=$HOME/.GVim-v8.2.2451.glibc2.15-x86_64.AppImage
> $
> $ vimV=$($vim --version)||echo handle error here #without
> export, error is captured
> fuse: failed to exec fusermount: No such file or directory
> open dir error:
> On Feb 5, 2021, at 3:40 PM, Alex fxmbsw7 Ratchev wrote:
>
> im sorry, in my terminal there is no unescaped ( or at all ) '(' in the
> regex
There are no parentheses in the gawk command I sent. It is identical
to the one you sent initially.
> see the display problem is..
>
> bash-5.1# bash -x
> On Feb 5, 2021, at 3:02 PM, Alex fxmbsw7 Ratchev wrote:
>
> i tried to report, that i tried to set the var new, but it didnt work so
> second alias | source run returned same two firstly aixz=( .. ) defined
> elements again
> and the gawk which catched the first aixz=( .. but not the second,
101 - 200 of 241 matches
Mail list logo
