bug tool, I’m not sure if this is actually a
bug. If you consider the following:
NickChambers-iMac:~ Nick$ type command
command is a shell builtin
This means that when you execute `command false`, false is executed in a child
subshell and command is executed in the current shell, and both retu
On 4/1/18, 5:54 AM, "bug-bash on behalf of Martijn Dekker"
wrote:
$ bash -c 'trap "echo WHOA" ERR; command false'
WHOA
WHOA
Expected output: just one WHOA (as on *ksh, zsh)
Thanks,
- M.
Please use the bashbug tool to submit the bug, so those that look
On 3/2/18, 9:03 AM, "bug-bash on behalf of Koncz, Istvan (Extern)"
wrote:
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='l
On Mon, Feb 12, 2018 at 6:33 PM, Chet Ramey wrote:
>
> Because, as I said in my original reply, readline understands how to
> complete inside quoted strings. If point is after the `b', for instance,
> and you hit TAB, readline scans back to the open quote and passes
> "p/foo/a b" to the completion
On Wed, Feb 7, 2018 at 11:12 PM, Chet Ramey wrote:
>
> You might try, as an intermediate step, removing `'' and `"' from
> $COMP_WORDBREAKS and seeing how that works. I would be interested if it
> affected readline's ability to complete within quoted strings.
>
I have tried this, and it works ok
On Wed, Feb 7, 2018 at 10:56 PM, Chet Ramey wrote:
> On 2/6/18 3:52 PM, Nick Patavalis wrote:
>>
>> In any case, splitting it like:
>>
>> foo | --bar | =" | baz" aa bb
>>
>> (the last part a single word) does not look reasonable to me (even if
&
Hi,
Thank you for your reply.
I'm not sure I understand everything, other than basically... "that's
how readline does it".
I don't suggest there's a bug in readline, but I don't understand, for
example, why
foo --bar "baz" aa bb
is ok to be split like:
foo | --bar | "baz" | aa | bb
while
I witnessed the following in the word-splitting results passed to
custom completion functions. The word splitting performed goes haywire
when it sees the =' (equal, quote) or =" (equal double-quote)
character sequences. From this point on, practically no word-splitting
is performed. As these sequen
ts for all processes
+status is zero. If ID is a job specification, waits for all processes
in that job's pipeline.
If the -n option is supplied, waits for the next job to terminate and
---
Nick Pongratz
Systems Engineer
Singlewire Software
Hello Chet and Eduardo,
thank you very much for your replies. Everything is crystal clear now.
Sorry for the 'wrong alarm' (:
Best,
Nick
On 20/12/2016 20:24, Chet Ramey wrote:
On 12/20/16 11:11 AM, Nick wrote:
i came up with a weird behavior of ssh+bash on my Debia
cuted with different
flags while being called from ssh versus a user), but as far as i understand,
the same things should be (or not) sourced.
Best,
Nick
Please find /etc/bash.bashrc, /etc/profile and my home directory under
this link: www.katastrofi.eu
e extender.
Sorry for the noise.
Nick
On 16/02/16 10:19, Bob Proulx wrote:
Nick Warne wrote:
I was in a SSH session, and checking something inadvertently issued:
> nano /var/log/messages | grep a
(I was searching for something else than an 'a', but the above example shows
the iss
from another terminal to get out of it.
I don't know if this behaviour is expected or me being stupid, or
something else going on.
Regards,
Nick
--
Gosh that takes me back... or is it forward? That's the trouble with
time travel, you never can tell."
-- Doctor Who "Androids of Tara"
be missing something. Can someone explain
why the first 2 examples do not exit on the error in the expansion?
*__*
*Nick Stoughton*
*Aether Things Inc *
*San Francisco*
+1 (510) 388 1413
The problem is that the link under [promptvars] points to
http://www.gnu.org/software/bash/manual/html_node/Controlling-the-Prompt.html#Controlling-the-Prompt,
and not to the link mentioned above.
*__*
*Nick Stoughton*
*Aether Things Inc *
*San Francisco*
+1 (510
On 2014-09-26 08:51 -0600, Eric Blake wrote:
> On 09/26/2014 08:45 AM, Nick Bowler wrote:
> > On 2014-09-25 15:08 -0700, Linda Walsh wrote:
> >> Eric Blake wrote:
> >>> Where I'm coming from is that in portable shell programming, you _can't_
> >>&g
-
standard assignments like this:
foo=$1; export foo
are not portable to bash, and may fail to work correctly depending on
the user's input.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
Hello,
I can not help too much on the "bug" side, but I would like to give a
tip regarding the situation you describe.
Often I've the same caveats about how my code will be used in a future
without my control...
If you know for sure, what makes the code unreliable, in this example
the /proc subs
On 4 March 2013 14:51, Chet Ramey wrote:
>
> This isn't accurate. Run the following script:
>
> foo()
> {
> echo foo
> }
> bar=quux
>
> readonly foo
> readonly bar
>
> readonly
>
> In addition to the built-in bash readonly variables, both bar and foo will
> be listed.
Maybe I'm wrong, bu
Hello,
Sorry if this has been reported earlier, but I can't find nothing
related in the archives.
$ help readonly | grep -- '-p'
readonly: readonly [-aAf] [name[=value] ...] or readonly -p
-pdisplay a list of all readonly variables and functions
$ echo $B
Hi Chet,
I was able to solve the problem; I had accidentally set my bashrc file
to source itself upon startup, which caused the segmentation fault.
Changing the file fixed the problem as far as I can tell.
Thanks for following up.
Thanks,
Nick
On Mar 31, 2012, at 8:51 PM, Chet Ramey wrote
thanks eric and mike for your quick reply and suggestions =)
2012/1/3 Eric Blake
> On 01/03/2012 06:48 AM, nick humphrey wrote:
> > Description:
> > i dont know if the bug is a bash bug or openssl or echo, but
> when i
> > echo a string and pipe it to openssl,
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' -DC$
uname output: Linux buildserver 2.6.27-11-server #1 SMP
From: Nick Hobson
To: bug-bash@gnu.org
Subject: Bash crashes if you try to mapfile into an associative array
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686&
Nick Brown wrote:
> Currently if the environmental variable is not set then
> DEBUGGER_START_FILE defaults to this;
>
> configure.in: DEBUGGER_START_FILE=
> ${ac_default_prefix}/lib/bashdb/bashdb-main.inc
>
> However looking at the bashdb package Makefiles I note that
>
share/bashdb/bashdb-main.inc"
but I'm sure someone that understands autoconf/automake better can
correct this.
Thanks,
Nick
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
my bug is not as much with bash as it is with apple.
i was using my mac, until a point where it said please restart, i restarted
and it booted back into bash, and has been doing so ever since.
i dont know how to solve this, maybe you guys have a solution?
__
my bug is not as much with bash as it is with apple.
i was using my mac, until a point where it said please restart, i restarted
and it booted back into bash, and has been doing so ever since.
i dont know how to solve this, maybe you guys have a solution?
__
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: i686-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/loc
r-line
finished sourcing B.sh
[EMAIL PROTECTED]:~>
See that the error message says that the error occured on line 3 of A.sh,
when in fact the error occured on line 3 of B.sh
-Nick Hoffman
[EMAIL PROTECTED]
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Lese selbst:
http://www.my-rocknord.de/viewtopic.php?t=1018&sid=3ce6385b1dee88cb02447f566a2da68d
.. damit Sie nicht als der erste Kanzler in die deutsche Geschichte eingehen,
der Untertanen verboten hat, aus ihren Fenstern auf die Strasse zu gucken -
selbst Nazis und Stalinisten haben niemals ei
31 matches
Mail list logo
