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
(the
words still appear on the command line). This was not occurring for me in the
3.x series of Bash.
Repeat-By:
Write this text on the command line: "sample text sample text sample
text sample text sample text". Start pressing ctrl-W and notice it takes a few
kill-words before the words start disappearing.
--Matt Zyzik
lprit line is:
echo "$REPLY"
It should instead be:
printf %s\\n "$REPLY"
In the current state of the script, lines like "-n" or "-e" won't get
printed.
The question I have is why couldn't echo have a -- flag? Is it for POSIX or
some other kind of compatibility reasons? Is there any easier way to accomplish
what I want other than printf %s\\n "$var"?
--Matt
mentioned "ls -adl exampl*/**" command should work the same
as "ls -adl examples/**"; however, as shown above, the behavior of the former
command is wrong. The commands work properly in both KornShell and Z shell.
--Matt Zyzik
g output in all 3 shells (ignore leading whitespace):
''good morning
Can I request comment? Thank you.
--Matt Zyzik
Hi,
In section 3.5.1 Brace Expansion of the Bash Reference Manual,
"sequence" is misspelled "seqeunce".
--
Matt Kraai
https://ftbfs.org/kraai
diff -C2 -r bash-4.2~/doc/bashref.texi bash-4.2/doc/bashref.texi
*** bash-4.2~/doc/bashref.texi 2011-04-04 20:30:51.0 -0
The first bug is in the bash(1) man page. In the SHELL GRAMMAR ->
Compound Commands -> [[ expression ]] section: "The return value is
0 if the string matches or does not match the pattern, respectively,
and 1 otherwise." This sentence is unclear. It is likely that
"respectively" maps "match
../.. from /home/m_kraai refers to the root directory, but there's no
entry in the root directory (using lstat) whose device and inode are
the same as /fs/hd0-qnx-2 (which is what .. refers to).
Repeat-By:
Logging in with
ot;/path/to/classes" com.choicestream.foo
I don't understand the reason for the discrepancy, and searching for "bash
quotes" gives me a lot of bash.org nonsense.
Thanks!
--
Matt Kane : [EMAIL PROTECTED]
AIM: mkbatwerk
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
bug-bash,
I have a few issues to address, that I arrived at recently. None of them are
necessarily bugs.
1. I noticed bash variables don't support null characters (0x00). This is
unlike perl and other languages. Will this ever change? Have people requested
or wanted this feature?
2. $(
[01;32m\]\u \[\033[01;31m\]- \[\033[01;34m\]\w\[\033[00m\]]$ '
--Matt
o many
times that it goes passed the width of the terminal and the words begin
to appear on the next line. (Open xterm at its default width to do
this.) At that point, keep hitting either Alt-Bksp or Ctrl-W until you
see bash not refreshing properly.
--Matt
locale information to `bashbug'; I can tackle the
> problem of making sure people actually use it to report bugs later.
The patch fixed the issue for me. And yes, I wasn't using a multibyte
locale.
--Matt
in siglist.c, the problem is fixed.
--
Matt http://ftbfs.org/
On Tue, Apr 21, 2009 at 08:02:00AM -0400, Greg Wooledge wrote:
> On Fri, Apr 17, 2009 at 08:52:16AM -0700, Matt Kraai wrote:
> > Using nm, I found that _ was undefined in siglist.o. If I include
> > bashintl.h in siglist.c, the problem is fixed.
>
> Yeah, I reported this e
The above-mentioned "ls -adl exampl*/**" command should work the
>> same as "ls
>> -adl examples/**"; however, as shown above, the behavior of the former
>> command is wrong. The
>> commands work properly in both KornShell and Z shell.
>>
>&
in the current directory and all
subdirectories. With the latest Bash, it only lists *.cs files in
subdirectories. The *.cs files in the current working directory are
ignored.
I think this is a bug. Again, "ls -adl **/*.cs" is now _not_ picking up
*.cs files in the current working directory.
--Matt
On Mon, May 18, 2009 at 10:04:06PM -0400, Mike Frysinger wrote:
> On Monday 18 May 2009 21:14:18 Matt Zyzik wrote:
> > Previously, the behavior of globstar mimicked that of ksh/zsh for such a
> > command: "ls -adl **/*.cs".
> >
> > Now I've upgraded to Bas
lves the issue, and I couldn't find any regressions.
--Matt
vcs solution as it produces context diffs by default and you have to
> purposely change it to do otherwise.
>
> Maintainers, I'd really like to hear your thoughts on this matter. If
> the diffs are produced as -p1 unified diffs, then downstreams who do
> convert from -p0 context won't have to, and distros who work around it
> won't either.
>
> Regards,
>
> Marty
>
Greetings,
Speaking for the CRUX maintainers, we don't have a preference. Whatever
works best for upstream.
Regards,
Matt
pEpkey.asc
Description: application/pgp-keys
20 matches
Mail list logo
