freundlichen Grüßen / Med vennlig hilsen
===
Thomas Dreibholz
Simula@OsloMet -- Simula Metropolitan Centre for Digital Engineering
Centre for Resilient Networks and Applications
Pilestredet 52
0167 Oslo, Norway
-
I can confirm that the patch resolves all the issues I had.
Thank you very much for your help, it is very appreciated.
On 10/15/24 11:08 AM, Thomas Oettli wrote:
> Got it, I just backported your patch to Bash 5.2 and it fixed the issue on
> my build host.
> I will roll out the patched v
?
Von: Chet Ramey
Gesendet: Dienstag, 15. Oktober 2024 16:24
An: Thomas Oettli ; bug-bash@gnu.org
Cc: chet.ra...@case.edu
Betreff: [EXT] Re: AW: Re: AW: Re: read command sometimes misses newline on
timeout
CAUTION: This email originated from outside the SFS organization. Do not follow
That sounds promising. Is the fix somewhere accessible for me? I would gladly
test it.
- Thomas
your help.
*
Thomas
Von: Martin D Kealey
Gesendet: Dienstag, 8. Oktober 2024 06:23
An: Martin D Kealey
Cc: Thomas Oettli ; bug-bash
Betreff: [EXT] Re: read command sometimes misses newline on timeout
CAUTION: This email originated from outside the SFS
.
Von: alex xmb sw ratchev
Gesendet: Montag, 7. Oktober 2024 21:50
An: Thomas Oettli ; bash list
Betreff: [EXT] Re: read command sometimes misses newline on timeout
CAUTION: This email originated from outside the SFS organization. Do not follow
guidance, click links
I know that it works in that case.
This is just an example that tries to force read into the same situatiation
that I hit in a real world example in which I don't control the input.
Von: alex xmb sw ratchev
Gesendet: Montag, 7. Oktober 2024 19:17
An: T
a
few seconds
with the following output:
Invalid line: TESTTEST
Von: alex xmb sw ratchev
Gesendet: Montag, 7. Oktober 2024 16:41
An: Thomas Oettli
Cc: bug-bash@gnu.org ; chet.ra...@case.edu
Betreff: [EXT] Re: read command sometimes misses newline on timeo
there, I would gladly change it. But I currently don't see
any way how to handle this properly from the script side.
Please also see the answer from Martin D Kealey, I think he is on to something:
https://lists.gnu.org/archive/html/bug-bash/2024-10/msg7.html
On 10/4/24 8:18 AM, Thomas O
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -O2 -pipe
uname output: Linux testserver 6.6.47-gentoo #1 SMP Tue Aug 20 09:38:16 CEST
2024 x86_64 Intel(R) Xeon(R) Gold 6242 CPU @ 2.80GHz Genuin
l/Config.pm:6077):
6077: if ( defined $ENV{$param} ) {
DB<9>
Shorewall::Config::export_params(/usr/share/shorewall/Shorewall/Config.pm:6078):
6078: next if $value eq $ENV{$param};
DB<9> V ENV[param]
$| = 1
$^A = ''
$^D = 0
$1 = 'ENV[param]'
%ENV = (
'CCACHE_DIR' => '/var/cache/ccache'
'CONFIG_PROTECT' => '/usr/share/gnupg/qualified.txt'
'CONFIG_PROTECT_MASK' => '/etc/sandbox.d /etc/terminfo'
'EDITOR' => '/bin/nano'
'GCC_SPECS' => ''
'HISTFILESIZE' => 1
'HISTSIZE' => 1
'HISTTIMEFORMAT' => "[\e[36m%F %T\e(B\e[m]: "
'HOME' => '/root'
[...]
--
Regards,
Thomas
11: Numerical result out of range
9223372036854775807
yes
$ /usr/bin/printf '%d\n' 111 && echo yes || echo no
/usr/bin/printf: ‘111’: Numerical result out of range
9223372036854775807
no
--
typedef struct me_s {
char na
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall
uname output: Linux fnord42 6.1.25-1rodete1-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.1.25-1rodete1
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
-fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat
-Werror=format-security -fstack-clash-protection
-fcf-pro
On 1/10/21 6:00 PM, bug-bash-requ...@gnu.org wrote:
Message: 3
Date: Sun, 10 Jan 2021 16:49:50 +0100
From: Ángel
To: bug-bash@gnu.org
Subject: Re: non-executable files in $PATH cause errors
Message-ID:
<94646752576f053515ac2ba4656fe0c895f348ce.ca...@16bits.net>
Content-Type: text/plain
On Wed, 23 Sep 2020 at 14:24, Chet Ramey wrote:
> "Expanded and executed similarly to BASH_ENV when an interactive shell is
> invoked in POSIX Mode."
>
Yes, that's better than my suggestions, thanks!
--
https://rrt.sc3d.org
The documentation says:
'ENV'
Similar to 'BASH_ENV'; used when the shell is invoked in POSIX Mode
(*note Bash POSIX Mode::).
However, as described elsewhere in the manual, BASH_ENV is used
specifically for non-interactive shells, whereas ENV is used specifically
for interactive shells.
Hello,
I noticed a small typo in the documentation on conditional
expressions. The typo is visible in the man page bash(1), where
it says:
The test abd [ commands determine their behavior based on
Most likely, 'abd' should be 'and' instead.
Greetings,
Thomas Fischer
arly don't like it, but our opinions only matter to us.
OK :(
Thank you for the explanation!
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
signature.asc
Description: OpenPGP digital signature
ay, back to bash:
So you are rejecting this patch, right? Maybe update man page at least
to clarify that "\H" in contrast to "\h" is supposed to return the same
value but _unfiltered_?
Thanks.
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 563
o
hostname only (no FQDN) and set domain option in /etc/resolv.conf for
example for FQDN. But maybe I am missing something.
Thanks.
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
signature.asc
Description: OpenPGP digital signature
At the moment, \h and \H used in prompt PS1 or PS2 will actually return
the same value while manpage claims that \h should return hostname up to
the first '.' (like `hostname`) and \H should return full hostname (like
`hostname -f`).
This commit will make bash use the same API like hostname comman
test.sh: line 5: bar=${${foo}_blah}: bad substitution
I run after the failing_function!
Rest of the script
Is my expectation wrong? I am really wondering that the script will
continue but not in the current if clause...
Tested with:
> GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)
--
:\n:g' |
> bash
> bash: line 2: no match: /foo/bar/*
> alive
> $ echo "set -e; shopt -s failglob; echo /foo/bar/*; echo alive; " | sed 's:;
> :\n:g' | bash
> bash: line 3: no match: /foo/bar/*
> $
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
signature.asc
Description: OpenPGP digital signature
From: thomas
To: bug-bash@gnu.org
Subject: Sequence Brace Expansion Crash
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 13 April 2017 at 22:05, Reuben Thomas wrote:
>
> On 13 April 2017 at 21:17, Chet Ramey wrote:
>
>> On 4/13/17 3:57 PM, Reuben Thomas wrote:
>>
>> > Meanwhile, in the valgrind bug report, Mark Wielaard observed:
>> >
>> > "I think the
On 13 April 2017 at 21:17, Chet Ramey wrote:
> On 4/13/17 3:57 PM, Reuben Thomas wrote:
>
> > Meanwhile, in the valgrind bug report, Mark Wielaard observed:
> >
> > "I think the problem is that bash not only has its own malloc/free
> > implementation (valgr
Here they are. I guess you probably won't care about them as as far as I
can see they are all one-off allocations at initialization:
==1289== 276 bytes in 1 blocks are definitely lost in loss record 230 of 249
==1289==at 0x4C2DB2F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so
On 13 April 2017 at 16:46, Chet Ramey wrote:
> On 4/13/17 11:41 AM, Reuben Thomas wrote:
>
> > This is not the result I obtained. I simply ran gdb on the bash binary,
> > valgrind was not involved.
>
> If you didn't build the binary yourself,
I did, from git ma
O
n 13 April 2017 at 16:27, Chet Ramey wrote:
> On 4/13/17 11:18 AM, Reuben Thomas wrote:
> > On 13 April 2017 at 16:11, Chet Ramey > <mailto:chet.ra...@case.edu>> wrote:
> >
> >
> > I see no reason why, since all of these things are defined in the
On 13 April 2017 at 16:11, Chet Ramey wrote:
>
> I see no reason why, since all of these things are defined in the same
> file and are statically linked, `free' would resolve to the glibc free
> when malloc resolves to the bash malloc.
So this is the real problem?
Do you have any suggestions
O
n 13 April 2017 at 15:33, Reuben Thomas wrote:
> On 12 April 2017 at 15:49, Chet Ramey wrote:
>
>>
>> It's a false positive, or a bug in valgrind. I took a quick look. There's
>> one place in this code path where free() gets called.
>
>
>
On 12 April 2017 at 15:49, Chet Ramey wrote:
>
> It's a false positive, or a bug in valgrind. I took a quick look. There's
> one place in this code path where free() gets called.
Julian Seward (valgrind author) pointed out:
"
…
what you report is symptomatic of bash
using its own mall
On 13 April 2017 at 09:15, Reuben Thomas wrote:
>
> Having confirmed Chet's analysis with a few printfs added to bash (i.e.
> just to check the address being allocated and the one complained about were
> the same) I've filed a bug report against valgrind:
> https://bug
On 12 April 2017 at 17:58, Hanno Böck wrote:
> On Wed, 12 Apr 2017 14:59:26 +0100
> Reuben Thomas wrote:
>
> > frequently, it's the only tool that shows up bugs of this sort, as
> > it's rather more powerful than a debugging malloc library.)
>
> Try addres
On Apr 12, 2017 4:56 PM, "Chet Ramey" wrote:
[snip]
> Maybe update the Debian bug report you cited as well. There's still stuff
> there from 2005.
The report is from December 2016. I can't find "2005" in the page.
I'll certainly send an update to point to the upstream bug I file.
O
n 12 April 2017 at 15:49, Chet Ramey wrote:
>
> It's a false positive, or a bug in valgrind. I took a quick look. There's
> one place in this code path where free() gets called. Here's the trace:
>
[analysis snipped]
Thanks very much, looks like it's time for me to file a Valgrind bug re
O
n 12 April 2017 at 14:50, Chet Ramey wrote:
> On 4/12/17 8:57 AM, Reuben Thomas wrote:
> > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849517
> >
> > I can reproduce this also in bash 4.3 as supplied with Ubuntu 16.04, and
> > in a build of 4.4 from
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849517
I can reproduce this also in bash 4.3 as supplied with Ubuntu 16.04, and
in a build of 4.4 from source on my Ubuntu system.
As stated in the bug report, the bug causes problems beyond bash, as it
causes build systems to think that val
The default HISTSIZE and HISTFILESIZE have been set for as long as I can
remember (and the repo only seems to back to bash 3.2).
For those concerned about privacy or security, 500 lines is probably too
much.
For those concerned about disk space, it's hard to come up with a sensible
default. My ro
On 18 January 2016 at 22:21, Chet Ramey wrote:
> On 1/18/16 11:53 AM, Reuben Thomas wrote:
>
> > So, how about instead interpreting a missing/0 date as a NaD (Not A
> Date),
> > rather as readline does anyway with time 0, and providing a slightly more
> > meaningf
[
Forwarding reply erroneously not sent to the list.]
On 15 January 2016 at 15:26, Chet Ramey wrote:
> On 1/11/16 11:54 AM, Reuben Thomas wrote:
> > On 11 January 2016 at 14:22, Chet Ramey > <mailto:chet.ra...@case.edu>> wrote:
> >
> > For a history f
On 11 January 2016 at 14:22, Chet Ramey wrote:
> For a history file without any timestamps, using
> the current default and setting the history entry timestamp to the current
> time is more appropriate.
>
Why is that? The only similar thing I can think of is file systems, where
if you zero the
On 8 January 2016 at 04:21, Eduardo A. Bustamante López
wrote:
>
> I now understand your points.
>
Thanks very much for taking a look at this.
> dualbus@hp ...src/gnu/bash % cat ~/.bash_history
> echo 1
> #1452197044
> echo a; sleep 1
> #1452197045
> echo b; sleep 1
>
On 7 January 2016 at 20:07, Eduardo A. Bustamante López
wrote:
> (2) The history should be ordered monotonically (increasing?)
>
Yes, and it's not at the moment (or wasn't, until I added timestamps to
every line in my history), because the lines at the start of the history,
with no timestamp, w
are passed then the script fails. It's surprising the
error behavior diverges depending upon setting an empty array or non-empty
array.
*-James Thomas Moon*
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 "AFTERPROM
s feature, and maybe even supply a patch if I had
a clue where to hook it in...
Thanks and kind regards,
Thomas
At least in bash 4.3, the documentation for history -a says:
Append the new history lines (history lines entered since the
beginning of the current Bash session) to the history file.
This is unfortunately misleading, since it suggests that the technique of
adding "history -a"
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-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
bug-bash-requ...@gnu.org wrote:
>Send bug-bash mailing list submissions to
> bug-bash@gnu.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/bug-bash
>or, via email, send a message with subject or body 'help' to
> bug-bash-
Yep, that fixed the problem, thank you !
2014-09-08 20:46 GMT+02:00 Chet Ramey :
> On 9/7/14, 6:40 PM, micka...@gmail.com wrote:
>
>> Bash Version: 4.3
>> Patch Level: 24
>> Release Status: release
>>
>> Description:
>> Given the following script (test.sh) :
>>
>> #!/bin/bash
>>
ts way into
Ubuntu 14.04 LTS released in two weeks, so it will probably stay for a
while.
Best regards
Thomas
On 18 March 2014 08:04, Linda Walsh wrote:
>
>
> Chet Ramey wrote:
>
>> Because the execution fails in a child process. You'd be able to fix it
>> for that process, but would do nothing about the contents of the parent
>> shell's hash table.
>>
>> The way the option works now is to check the has
On 17 March 2014 20:46, Chet Ramey wrote:
> Because the execution fails in a child process. You'd be able to fix it
> for that process, but would do nothing about the contents of the parent
> shell's hash table.
>
Thanks for the explanation.
--
http://rrt.sc3d.org
On 17 March 2014 20:30, Chet Ramey wrote:
> On 3/17/14 10:17 AM, Dave Rutherford wrote:
> > On Mon, Mar 17, 2014 at 10:12 AM, Chet Ramey
> wrote:
> >> On 3/15/14 2:44 PM, Reuben Thomas wrote:
> >>> On 15 March 2014 18:23, Chet Ramey >>> <mailto:
On 17 March 2014 14:12, Chet Ramey wrote:
> On 3/15/14 2:44 PM, Reuben Thomas wrote:
> > On 15 March 2014 18:23, Chet Ramey > <mailto:chet.ra...@case.edu>> wrote:
> >
> > It's not been a problem, really. The existence of the `checkhash'
> opt
On 15 March 2014 18:23, Chet Ramey wrote:
> It's not been a problem, really. The existence of the `checkhash' option
> has been enough. How often do you remove binaries in directories in $PATH?
>
Fairly often: I frequently rename or retire scripts in my per-user bin
directory.
Since bash is h
On 14 March 2014 18:23, Chet Ramey wrote:
> On 3/14/14 12:11 PM, Reuben Thomas wrote:
> > Tested in bash 4.3.
> >
> > $ foo
> > ... a command is run
> > $ hash
> > hits command
> >0 /home/rrt/bin/foo
> > $ rm `which foo`
> > $ which f
Tested in bash 4.3.
$ foo
... a command is run
$ hash
hits command
0 /home/rrt/bin/foo
$ rm `which foo`
$ which foo
/usr/bin/foo
$ foo
bash: /home/rrt/bin/foo: No such file or directory
Why doesn't bash just remove the hashed path and do a normal PATH search? I
have to remove it manually.
--
ring a bell with anyone or is this most likely a distro-specific
bug?
Info:
$ bash --version
GNU bash, version 3.2.51(1)-release (x86_64-suse-linux-gnu)
> rpm -q -a|grep bash
bash-3.2-147.9.13
$ cat /etc/issue
Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r (\l).
I attach t
h.1 2013-08-21 19:13:58.541953745 +0200
@@ -7307,13 +7307,6 @@
.BR SIGHUP .
If no
.I jobspec
-is present, and neither the
-.B \-a
-nor the
-.B \-r
-option is supplied, the \fIcurrent job\fP is used.
-If no
-.I jobspec
is supplied, the
.B \-a
option means to remove or mark all jobs; the
--
Thomas Hood
In function sh_realpath() defined in lib/sh/pathphys.c, the arguments
passed to sh_makepath() are inverted. This makes the sh_realpath()
fail when is not an absolute path because the expected
concatenation is /, not the reverse.
This problem does not look to be critical, at least in Bash 4.1,
bec
sources if you think it's worth it.
Kind regards,
Julien
>From dff9b244b233415d5081c3e4b40500e01929c74a Mon Sep 17 00:00:00 2001
From: Julien Thomas
Date: Mon, 27 May 2013 17:45:11 +0200
Subject: [PATCH 1/3] ln: Whitespace cleanup, remove tabulations
---
ln.
(Checked against bash 4.2; for some reason, the manual on gnu.org is only 4.1.)
The top node, "Bash Features", says:
"The following menu breaks the features up into categories based upon which
one of these other shells inspired the feature."
But the following menu doesn't seem to bear that out.
On Jan 18, 5:22 am, Greg Wooledge wrote:
> On Wed, Jan 18, 2012 at 01:19:20PM +0900, Teika Kazura wrote:
> > If the
> > entire script is read at invocation, then why should / does
> > modification affect? Is it a bug?
>
> The entire script *isn't* read at invocation. Bash just reads a little
> bi
d, if there is a way for bash to not display special characters
on the interactive line,
i suppose it can be useful to know how to do that in many cases, for example if
i switch on a new platform, waiting for making special characters to be
displayed correctly
(Is it correct english enough ?)
--
Téléassistance / Télémaintenance
(adresse temporaire)
http://biocer.fr/invites/thomas-de-contes/
ke a workaround myself ? very
good news :-))
(How can I know when it will be available ?)
--
Téléassistance / Télémaintenance
(adresse temporaire)
http://biocer.fr/invites/thomas-de-contes/
Le 25 août 2011 à 14:36, Greg Wooledge a écrit :
> On Wed, Aug 24, 2011 at 06:51:32PM -0700, Linda Walsh wrote:
>> BTW, Thomas -- what is the Character that comes after 'De' in your
>> name? I read it as hex '0xc282c2' which doesn't seem to be valid
Le 16 mai 2011 à 17:02, Chet Ramey a écrit :
> On 5/9/11 10:46 AM, Thomas De Contes wrote:
>> 1
>> - execute
>> PS1="&# $PS1"
>> - drag & drop the file with the accent
>> - use "top arrow" and "bottom arrow" to move in the
Hello,
In bash-4.2 in execute_cmd.c there is a usage of job_control that
isn't enclosed in "#if defined(JOB_CONTROL)" / "#endif". This causes a
compile failure on Minix since job_control is only defined if
JOB_CONTROL is defined. Patch attached.
-Thomas
--- execute_cmd.c
my home internet is hooked up (which should be any day now...).
On Sat, May 28, 2011 at 3:42 PM, Chet Ramey wrote:
> On 5/27/11 6:20 PM, David Thomas wrote:
>> Hi Chet,
>>
>> Thank you for the response, and the attempt at assistance.
>>
>> I was unaware of the POS
short term, I was able to get the behavior I want by overriding
fc in the script in question, but I still think default behavior is
ugly.
Thanks again for the response, and I'm interested in your further thoughts.
- David
On Thu, May 26, 2011 at 9:09 AM, Chet Ramey wrote:
> On 5/23/11 1
Hi all,
In using bash over the years, I've been quite happy to be able to hit
ctrl-x ctrl-e to pull up an editor when my input has grown too
complicated.
When using read -e for input, however, the behavior I find makes a lot
less sense: the input line is still opened in an editor, but the
result
Le 9 mai 2011 à 20:21, Greg Wooledge a écrit :
> On Mon, May 09, 2011 at 04:46:14PM +0200, Thomas De Contes wrote:
>> Description:
>>
>> 1
>> when i do
>> PS1="&# $PS1"
>> then I have problems since there is some accents in my command lin
x27;
-DCONF_VENDOR='apple'
-DLOCALEDIR='/Users/thomas/Administration-ordinateur/autoinstall/macports/share/locale'
-DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -DMACOSX -I. -I. -I./include
-I./lib -I/Users/thomas/Administration-ordinateur/autoinstall/macports/include
-
verlaps. Using the memmove,
copying takes place as if an intermediate buffer was used,
allowing the destination and source to overlap.
Regards,
Thomas Kuschel, oe6tkt
--- old/y.tab.c2009-12-30 18:52:02.0 +0100
+++ y.tab.c2011-02-11 12:36:45.682266575 +0100
Hi,
bash has only 0.43% examples at the pleac project.
Pleac is the perl cookbook translated to other languages.
It would be nice if someone could improve it:
http://pleac.sourceforge.net/
Thomas
--
Thomas Guettler, http://www.thomas-guettler.de/
E-Mail: guettli (*) thomas-guettler + de
Hey All,
Not sure if this is a bug but logging anyway just in case.
Rgds,
Thomas
* The version number and release status of Bash (e.g., 2.05-release)
o GNU bash, version 3.00.16(1)-release-(i386-pc-solaris2.10)
* The machine and OS that it is running on (you may run /bashversion
U bash, version 4.1.7(2)-release (i486-slackware-linux-gnu)
On Slackware-13.1
I also verified this behaviour on:
GNU bash, version 4.1.5(1)-release (x86_64-pc-linux-gnu)
(Ubuntu Lucid)
Is this normal or expected?
Thanks
- --
Thomas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: freebsd6.2
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='freebsd6.2' -DCONF_MACHTYPE='i386-portbld-freebsd6.2'
-DCONF_VENDOR='portbld' -DLOCALEDIR='/usr/local/share/loc
nconsistent. And I absolutely understand why, as
there are multiple meanings for a poor little bracket ;->
On Mon, 03/29, 2010 02:51:18PM, Greg Wooledge wrote:
> On Mon, Mar 29, 2010 at 02:22:35PM +0200, Thomas Bartosik wrote:
> > Well OK, I understand. Still I think there should be
Well OK, I understand. Still I think there should be a difference in the man
page when it comes to brackets. When talking about arrays, the brackets are NOT
an option but mandatory.
(and it might be me being uneducated, but how to you print out the decimal
equivalent of binary 11 without using b
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
dap directory, there is no crash and it appears to
work.
As a temporary workaround, I am currently using a dynamically linked
bash.
Repeat-By:
bash-4.0$ ./config.status --version
bash config.status 4.0-release
configured by /home/thomas/src/bash-4.0/
ple can search for $! and find it),
> it was not accepted.
I support that such a patch is installed, as it makes navigating in the
manual easier for all those who don't know in which section to look for
$!, for example.
Regards,
Thomas
signature.asc
Description: Digital signature
The syntax for the "for" command is misleading, as although correct for
bash, it is not POSIX-compliant.
I am using GNU bash, version 3.2.48(1)-release (i486-pc-linux-gnu)
The man page says:
for name [ in word ] ; do list ; done
which conflicts with the POSIX syntax definition, given in
http
Hello!
On Thu, Jan 29, 2009 at 05:47:53PM +0100, Andreas Schwab wrote:
> Thomas Schwinge writes:
> > These three work as expected. But why doesn't the following one?
> >
> > tho...@dirichlet:~ $ sh -c 'if : 2> /dev/null < NONEXISTING_FILE; then
> &g
cho >&2 OK; fi'
OK
These three work as expected. But why doesn't the following one?
tho...@dirichlet:~ $ sh -c 'if : 2> /dev/null < NONEXISTING_FILE; then :;
else echo >&2 OK; fi'
(no output)
Regards,
Thomas
signature.asc
Description: Digital signature
can I send a WINCH signal to bash so that it recalculates the
correct values of LINES and COLUMNS after a font change?
Thanks
Thomas
ki.ubuntu.com/Spec/EnhancedBash as well as
however the examples given are all hardcoded, and (given the limitation
to specific terminal types) more/less work without requiring any modification
to bash.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
__
27;' show?
Regards,
Thomas
signature.asc
Description: Digital signature
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
n request (equiv. to VT100/ANSI/ECMA-48 DSR 6)
# u6 cursor position report (equiv. to ANSI/ECMA-48 CPR)
The feature won't work on some terminal types (Sun console for instance).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Configuration Information:
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/locale' -DPACKAGE='bash' -DSHELL
-DHAVE_CONF
iven on PuTTY's website has some problems).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
affects the bash
> shell? I fail to see a connection.
He wants `echo *' to not display these files anymore and so forth, I
guess.
Regards,
Thomas
signature.asc
Description: Digital signature
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
particularly the fact that it fails silently? (I didn't
investigate so far.)
Regards,
Thomas
signature.asc
Description: Digital signature
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
[EMAIL PROTECTED] wrote:
---
Message: 1
Date: Tue, 10 Oct 2006 16:08:05 -0500
From: mwoehlke <[EMAIL PROTECTED]>
Subject: How to detect bash?
To: bug-bash@gnu.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Anyone have any clever, VERY reliab
erun it with just a very few key-presses.
--
---
Thomas Mellman Tel: +49/8233/389-037
Creative Telcom Solutions
[EMAIL PROTECTED] Fax: +49/1212-5-115-48-103
___
Bug
From: schorpp
To: bug-bash@gnu.org,[EMAIL PROTECTED]
Subject: -see mail subject-
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i3
1 - 100 of 104 matches
Mail list logo
