nd, but why not?
Thanks,
-Mike
+1314,8 @@ get_comp_wordbreaks (var)
if (rl_completer_word_break_characters == 0 && bash_readline_initialized ==
0)
enable_hostname_completion (perform_hostname_completion);
- var_setvalue (var, rl_completer_word_break_characters);
+ FREE (value_cell (var));
+ var_setvalue (var, savestring (rl_completer_word_break_characters));
return (var);
}
--
Mike Stroyan <[EMAIL PROTECTED]>
Hi,
It seems some things are missing in the bash manual.
Notably definition of command and placements of coproc- and function-definition.
The section 'SHELL GRAMMAR' describes:
- simple-command
- pipeline
- list
- compound-command
- coproc
- function-definition
Simplified, a pipeline is:
On Tue, Feb 23, 2021 at 04:33:44PM -0500, Chet Ramey wrote:
> On 2/22/21 8:11 AM, Mike Jonkmans wrote:
> >
> > Hi,
> >
> > It seems some things are missing in the bash manual.
> > Notably definition of command and placements of coproc- and
> > function-
On Wed, Feb 24, 2021 at 12:08:50PM -0500, Chet Ramey wrote:
> On 2/23/21 7:31 PM, Mike Jonkmans wrote:
> > On Tue, Feb 23, 2021 at 04:33:44PM -0500, Chet Ramey wrote:
> > > On 2/22/21 8:11 AM, Mike Jonkmans wrote:
> > > >
> > > > Hi,
> > > >
On Thu, Feb 25, 2021 at 11:15:36PM +0100, Ángel wrote:
> On 2021-02-25 at 16:13 +0100, Mike Jonkmans wrote:
> >
> > Aren't grammars taught already in primary school? It is in the
> > Netherlands.
> > But i agree that it is a good thing to let the text not depend
On Thu, Feb 25, 2021 at 06:28:34PM -0500, Chet Ramey wrote:
> On 2/25/21 10:13 AM, Mike Jonkmans wrote:
> > Starting with 'Statements' might be an option.
>
> Maybe. Or a POSIX-like description that says a command can be a
>
> simple command
> list
> p
On Fri, Feb 26, 2021 at 02:54:07AM +0100, Ángel wrote:
> On 2021-02-26 at 00:45 +0100, Mike Jonkmans wrote:
> > On Thu, Feb 25, 2021 at 11:15:36PM +0100, Ángel wrote:
> >
> > Those grammars weren't all that different from yacc's grammar.
> > Just simpler and
On Fri, Feb 26, 2021 at 12:41:44PM -0500, Chet Ramey wrote:
> On 2/26/21 11:22 AM, Mike Jonkmans wrote:
>
> > I don't think that f.i. precedence was taught.
> > Although you get that with arithmetic, which also has a grammar.
>
> It's not taught as such. Kids to
grammar doesn't mention the word 'function'.
Posix does mention it, as reserved word recognized by 'some implementations'
and causing undefined behavior.
Regards, Mike Jonkmans
On Sun, Feb 28, 2021 at 05:06:37PM -0500, Chet Ramey wrote:
> On 2/28/21 12:38 PM, Mike Jonkmans wrote:
>
> > The manual page says:
> > If the function reserved word is used, but the parentheses are not
> > supplied,
> > the braces are required.
>
>
The -x option to ctags generates 'human readable' stuff that vim can not use.
This patch removes the -x and the '>$@', which is not needed.
Refer to https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ctags.html
Also introducing $(ETAGS) $(ETAGSFLAGS) and same fo
I assume that the TAGS and tags files will not go into the repo.
Regards, Mike Jonkmans
diff --git .gitignore .gitignore
index 1512a9ab..f09f4eac 100644
--- .gitignore
+++ .gitignore
@@ -113,3 +113,6 @@ examples/loadables/tty
examples/loadables/uname
examples/loadables/unlink
examples
On Mon, Mar 15, 2021 at 11:23:46AM -0400, Chet Ramey wrote:
> On 3/15/21 3:29 AM, Mike Jonkmans wrote:
> > I assume that the TAGS and tags files will not go into the repo.
>
> Why not? This is only the devel branch; they don't go into releases.
Adding tags/TAGS to the rep
On Mon, Mar 15, 2021 at 04:06:06PM -0500, Eric Blake wrote:
> But even if the upstream repo doesn't want to ignore a file in the
> (checked-in) .gitignore, you can always edit your (local-only)
> .git/info/exclude to exclude your extra files locally.
Thanks Eric, that is useful.
A 'make distclean' removes lib/readline/doc/Makefile
It is a handmade Makefile, so probably should not be removed.
Idem for maintainer-clean.
Regards, Mike Jonkmans
diff --git lib/readline/doc/Makefile lib/readline/doc/Makefile
index af5ee3e5..6bc2e5ea 100644
--- lib/readline/do
ho $BASH_VERSION
5.0.17(1)-release
$ alias n=bla
$ n() { type $FUNCNAME; }
$ declare -pf n
bash: declare: n: not found
$ declare -pf bla
bla ()
{
type $FUNCNAME
}
It is the same on 5.1.4(1)-release.
I would have expected that n was a defined function.
But I would not have bet on it.
Regards, Mike Jonkmans
k that the line
aval = expand_assignment_string_to_string (v, 0);
should be moved down below the next if-statement.
Because of the continue, there is a memory leak.
Regards, Mike Jonkmans
Configuration Information [Automatically generated, do not change]:
Machine: powerpc
OS: aix6.1.9.0
Compiler: gcc -maix64
Compilation CFLAGS: -g -Wno-parentheses -Wno-format-security
uname output: AIX aixutil07 2 7 00C07A304B00
Machine Type: powerpc-ibm-aix6.1.9.0
Bash Version: 5.0
Patch Level: 18
h/2017-04/msg00063.html
> https://lists.gnu.org/archive/html/bug-bash/2017-06/msg00052.html
There is also uselocale, newlocale, duplocale and freelocale.
The manual says POSIX.1-2008, so it should be reasonably portable.
Not sure if it is worth the trouble.
Regards, Mike Jonkmans
On Mon, Jul 26, 2021 at 03:57:16PM +0200, Alex fxmbsw7 Ratchev wrote:
> ..
..: command not found
Regards, Mike Jonkmans
ouble quotes
instead of single quotes. This might expose the script to the
translated
result. For compatibility reasons, this option is enabled by default.
Regards, Mike Jonkmans
ms to be the fastest:
f12 () { [[ "$1" =~ ${1//?/(.)} ]]; local arr=( "${BASH_REMATCH[@]:1}" ); }
time for ((i=1; i<=1; i++)); do f0 682390; done
real0m0,296s
user0m0,296s
sys 0m0,000s
Regards, Mike Jonkmans
On Tue, Aug 24, 2021 at 09:24:35AM -0400, Greg Wooledge wrote:
> On Tue, Aug 24, 2021 at 03:09:55PM +0200, Mike Jonkmans wrote:
> > This seems to be the fastest:
> > f12 () { [[ "$1" =~ ${1//?/(.)} ]]; local arr=( "${BASH_REMATCH[@]:1}" ); }
> > time for (
On Tue, Aug 24, 2021 at 04:16:46PM +0200, Léa Gris wrote:
> Le 24/08/2021 à 15:09, Mike Jonkmans écrivait :
> > This seems to be the fastest:
> > f12 () { [[ "$1" =~ ${1//?/(.)} ]]; local arr=( "${BASH_REMATCH[@]:1}" ); }
>
> Awesome Mike, would you like t
gt; 9
>
> Please help explain
Not a bug.
If you leave out the |tail -1', you will see that
the output of head -1 gets appended to that of tee.
--
Regards, Mike Jonkmans
Run command with args suppressing the normal shell function lookup.
Only builtin commands or commands found in the PATH are executed.
...
I think the hash lookup should be mentioned,
as the hash lookup is done before the builtin/PATH search, e.g.:
PATH=/
On Sun, Oct 31, 2021 at 03:33:07PM +0300, Oğuz wrote:
> On Sun, Oct 31, 2021 at 2:15 PM Mike Jonkmans wrote:
> > PATH=/dev/null
> > command -p hostname
> > hostname # executes /bin/hostname via the hash table
> >
> > I agree with OP that th
On Sun, Oct 31, 2021 at 05:23:03PM +0200, Oğuz wrote:
> 31 Ekim 2021 Pazar tarihinde Mike Jonkmans yazdı:
> >
> > Using the hash as alias for commands, that are not in your PATH,
> > seems risky though.
>
> Why? Risky how?
Risky, mostly on a cognitive level.
'c
On Sun, Oct 31, 2021 at 08:36:49PM +0300, Oğuz wrote:
> On Sun, Oct 31, 2021 at 7:07 PM Mike Jonkmans wrote:
> >
> > On Sun, Oct 31, 2021 at 05:23:03PM +0200, Oğuz wrote:
> > > 31 Ekim 2021 Pazar tarihinde Mike Jonkmans yazdı:
> > > >
> > > > Using
On Mon, Nov 01, 2021 at 09:09:19AM +0300, Oğuz wrote:
> On Sun, Oct 31, 2021 at 10:26 PM Mike Jonkmans wrote:
> > POSIX is also silent on this.
>
> I think ``Once a utility has been searched for and found [...], an
> implementation may remember its location and need not search
On Mon, Nov 01, 2021 at 12:21:41PM +0300, Oğuz wrote:
> On Mon, Nov 1, 2021 at 10:58 AM Mike Jonkmans wrote:
> > This wording does not cover it wholly, in my opinion.
> > Because when the utility's hashed path is not in $PATH,
> > then the utility should not have been s
(temporary) modified PATH comes from.
Good point!
> ps: should this be discussed for clarification in POSIX, I have no doubt
> which way the result would go.
There is the issue of 'command -p ...' changing the hash table.
Another issue is, the usage of hashed values
that a
>
> A mild annoyance at best, don't you think?
Mostly an annoyance, but it has potential to be a security issue.
Regards, Mike Jonkmans
mmand
"\e[200~": bracketed-paste-begin
## The initial escape is eaten, when pasting in insert mode:
"[200~": bracketed-paste-begin
## Start with the last 'set keymap' mode
set keymap vi-insert
"\e[200~": bracketed-paste-begin
Hope that it helps.
--
Regards, Mike Jonkmans
g.tar?(.!(sig|.*)))shopt
> -u extglob}xEOFResults in:
>
> bash: line 3: syntax error near unexpected token `('
>
> bash: line 3: `mapfile -t packages < <(printf "%s\n"
> "dir"/"dir"/"dir"/"{targetname}"-"${targetver}"-"${targetarch}".pkg.tar?(.!(sig|.*)))'
>
> Putting shopt options outside the function, but is this the wanted
> behaviour?
> ...
> Tobias Powalowski
--
Regards, Mike Jonkmans
l
refers to a website pointing out problems with gettimeofday.
That website was (presumably) written in 2010/09 :
https://blog.habets.se/2010/09/gettimeofday-should-never-be-used-to-measure-time.html
So it is not that new.
It is another special case in code, which may explain the slow uptake in tools,
many of which need to be portable.
--
Regards, Mike Jonkmans
On Fri, Mar 31, 2023 at 06:30:00PM +0200, Martin Schulte wrote:
> Hi Chet!
>
> > Thanks for the report. The synopsis should read
> >
> > cd [-L|[-P [-e]]] [-@] [dir]
> ^ ^
> But aren't these two brackets just superfluous?
Then -L would get the -e too.
--
Regards, Mike Jonkmans
p?id=1649
Thanks for the link.
And well done, kre!
--
Regards, Mike Jonkmans
ls; hash -td ls
And -d ignores -l:
hash ls; hash -ld ls
Conclusion
I would say that:
- Combining options should error;
- Except for an added -r, which first clears;
- 'hash -l x' shouldn't add, but print what 'hash -lt x' currently prints;
- 'hash -d x' a
On Mon, Sep 11, 2023 at 03:25:01PM -0400, Chet Ramey wrote:
> On 9/6/23 10:55 AM, Mike Jonkmans wrote:
> > The following 'hash -d' statements have different exit statuses.
> >
> > bash --noprofile --norc -c \
> > 'hash -d ls; echo $
On Wed, Sep 13, 2023 at 11:32:36AM -0400, Chet Ramey wrote:
> On 9/12/23 8:28 AM, Mike Jonkmans wrote:
> > On Mon, Sep 11, 2023 at 03:25:01PM -0400, Chet Ramey wrote:
> > > On 9/6/23 10:55 AM, Mike Jonkmans wrote:
...
> > > > 3) These option combinations should erro
12 years ago in devel
(10 years ago in master, bash 4.3).
Since then nobody disabled aliases or took the trouble of reporting.
Wouldn't it be opportune to remove the `--enable-alias' option?
Saves a couple of #ifdef's too.
--
Regards, Mike Jonkmans
pcomplete.c | 6 +++---
1
Hi,
The 'times' utility is not listed as a posix special builtin
in doc/bashref.texi
It can be fixed by changing:
@w{shift trap unset}
to:
@w{shift times trap unset}
--
Regards, Mike Jonkmans
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap01.html#tag_17_06
--
Regards, Mike Jonkmans
Thanks for the answers, Chet.
On Mon, Nov 06, 2023 at 02:28:24PM -0500, Chet Ramey wrote:
> On 11/6/23 10:48 AM, Mike Jonkmans wrote:
>
> > Q: Why check for regular builtins? That was already done in 1d.
> Implementations can provide other builtins. The check in 1d is only for
&
On Tue, Nov 07, 2023 at 09:39:33AM +0700, Robert Elz wrote:
> Date:Mon, 6 Nov 2023 14:28:24 -0500
> From:Chet Ramey
> Message-ID: <0ab6075e-22bf-43cd-992c-b2476f626...@case.edu>
>
> | On 11/6/23 10:48 AM, Mike Jonkmans wrote:
> | > Acco
On Tue, Nov 07, 2023 at 11:49:25AM -0500, Chet Ramey wrote:
> On 11/7/23 8:54 AM, Mike Jonkmans wrote:
...
> > > Look at https://www.austingroupbugs.net/view.php?id=854 for a discussion
> > > of this issue.
> > Thanks for the link, I find that very hard to read tho
On Wed, Nov 08, 2023 at 10:38:19AM -0500, Chet Ramey wrote:
> On 11/7/23 5:04 PM, Mike Jonkmans wrote:
>
> It depends on your requirements. If you want something that is easy to
> explain to users, you want to reduce the distinction between `intrinsics'
> and `regular built
On Wed, Nov 08, 2023 at 11:52:19PM +0700, Robert Elz wrote:
> Date:Tue, 7 Nov 2023 23:04:10 +0100
> From: Mike Jonkmans
> Message-ID: <20231107220410.gc27...@jonkmans.nl>
>
> | It makes sense to partition the builtins in three categories with
On Wed, Nov 08, 2023 at 10:42:20AM -0500, Chet Ramey wrote:
> On 11/7/23 5:37 PM, Mike Jonkmans wrote:
> > On Tue, Nov 07, 2023 at 11:49:25AM -0500, Chet Ramey wrote:
> > > On 11/7/23 8:54 AM, Mike Jonkmans wrote:
> > So the discussion is hidden. Hmm.
> Not hidden; if y
On Thu, Nov 09, 2023 at 10:12:06PM +0700, Robert Elz wrote:
> Date:Thu, 9 Nov 2023 14:21:35 +0100
> From: Mike Jonkmans
> Message-ID: <20231109132135.ga208...@jonkmans.nl>
>
> | If I am not mistaken, for POSIX compliance, both /bin and /usr/bi
On Fri, Nov 10, 2023 at 08:07:31PM -0500, Chet Ramey wrote:
> On 11/9/23 11:17 AM, Mike Jonkmans wrote:
> > On Thu, Nov 09, 2023 at 10:12:06PM +0700, Robert Elz wrote:
> >
> > On Ubuntu 22.04 `getconf path' returns /bin:/usr/bin
> > and these are symlinked.
> T
On Sat, Nov 11, 2023 at 08:31:14AM -0500, Greg Wooledge wrote:
> On Sat, Nov 11, 2023 at 09:14:41AM +0100, Mike Jonkmans wrote:
> > On Fri, Nov 10, 2023 at 08:07:31PM -0500, Chet Ramey wrote:
> > > On 11/9/23 11:17 AM, Mike Jonkmans wrote:
> > > > On Thu, Nov 09, 20
he first.
Returning to `shell-expand-line'.
As end user I would expect that, running shell-expand-line then accept-line,
would do the same as just an accept-line.
Quote removal is absolutely needed, otherwise expansions may mess up
the result when they introduce quotes.
I think that escaping is needed after quote removal in shell-expand-line.
--
Regards, Mike Jonkmans
On Thu, Feb 01, 2024 at 08:14:34PM -0500, Chet Ramey wrote:
> On 1/31/24 6:05 PM, Mike Jonkmans wrote:
>
> > The first sentence under EXPANSION may make you think otherwise:
> >Expansion is performed on the command line after it has been split into
> > words.
> &g
mode it might be nice if the cursor didn't move onto the
last character.
vi-insert mode: `ls *' cursur is after the `*'
then going to vi-command mode, the cursor moves onto the `*'.
This prevents the `glob-expand-word' from doing its thing.
--
Regards, Mike Jonkmans
On Fri, Feb 02, 2024 at 10:09:53AM -0500, Chet Ramey wrote:
> On 2/2/24 8:12 AM, Mike Jonkmans wrote:
> > On Thu, Feb 01, 2024 at 08:14:34PM -0500, Chet Ramey wrote:
> > "There are seven kinds of expansion..." then three sentences later comes
> > quote removal. The
On Fri, Feb 02, 2024 at 09:50:46AM -0500, Greg Wooledge wrote:
> On Fri, Feb 02, 2024 at 03:39:54PM +0100, Mike Jonkmans wrote:
> > [ mkdir test; cd test; touch file1 file2 ]
> >
> > Going into `vi-command' mode on the line `ls *' puts the cursor on the `*
On Sat, Feb 03, 2024 at 03:43:45PM -0500, Chet Ramey wrote:
> On 2/2/24 9:39 AM, Mike Jonkmans wrote:
> > From the manual, glob-expand-word:
>
> glob-expand-word doesn't work that great in vi command mode, mostly for
> the reasons you suspect. What made you use it ov
On Sat, Feb 03, 2024 at 04:59:08PM -0500, Chet Ramey wrote:
> On 2/2/24 5:15 PM, Mike Jonkmans wrote:
> > On Fri, Feb 02, 2024 at 09:50:46AM -0500, Greg Wooledge wrote:
> > > On Fri, Feb 02, 2024 at 03:39:54PM +0100, Mike Jonkmans wrote:
> > > > [ mkdir te
## C-xq (let's assume it quotes the redirections)
$ printf "<%s>\n" x y
The original words before quote removal should be requoted.
Also when expansion introduces quotes:
$ x=\"
$ printf "$x\n" ## M-C-e-new (shell-expand-quoted?)
$ printf "\"\n"
$ printf $x\\n ## M-C-e-new
$ printf \"\\n
Oh well, I am happy with the undo :)
--
Regards, Mike Jonkmans
to a
> `declare' command when applied to a local variable at the current scope,
> even if there are no attributes to be displayed. Agreed?
>
> I am less convinced about outputting a `-g' for a global variable when
> called from a function scope, but I could be persuaded.
This would be logical.
Forgot the use case, but it was about a year ago that I needed this.
--
Regards, Mike Jonkmans
On Tue, Mar 19, 2024 at 02:24:34PM -0400, Chet Ramey wrote:
> On 3/19/24 11:50 AM, Mike Jonkmans wrote:
>
> > > Yes. There is one thing missing: the transformation should expand to a
> > > `declare' command when applied to a local variable at the current scop
tests show it seems to be working OK so far ...
-mike
signature.asc
Description: This is a digitally signed message part.
On Wednesday, February 02, 2011 21:49:38 Chet Ramey wrote:
> On 2/2/11 6:27 PM, Mike Frysinger wrote:
> > - lib/glob/smatch.c needs externs.h for mbsmbchar. seems like externs.h
> > could do with including bashtypes.h/command.h/general.h too since it
> > needs basic ty
ore people so
> everyone can help review and test before a stable release.
the 4.2 rc1 was announced on the list and garnered testing/feedback
-mike
signature.asc
Description: This is a digitally signed message part.
he original bug report uses variables in the pattern and quotes them to avoid
expansion of globs and such. but if the variable happened to be empty, things
no longer worked correctly.
-mike
signature.asc
Description: This is a digitally signed message part.
On Friday, February 18, 2011 23:17:11 Chet Ramey wrote:
> On 2/18/11 9:06 PM, Mike Frysinger wrote:
> > this simple code no longer works in bash-4.2:
> > $ f=abc; echo ${f##""a}
> > abc
> > same goes for ${f//""a} and ${f%%""c}, and per
ady told this guy to stop
using gcc-4.6 and using ridiculous CFLAGS/LDFLAGS if he wasnt going to assist
in figuring out the bugs.
-mike
signature.asc
Description: This is a digitally signed message part.
t; gcc: \: No such file or directory
>
> Kinda like that.
>
> Maybe it's gcc 4.6-prewhatever that's doing it. Maybe he's actually using
> some sort of "build system wrapper" that's broken. I don't know. I just
> recognize the symptom, not the cause.
the Gentoo ebuild double quotes the flags in env CPPFLAGS so that gcc
sets the strings correctly when compiling.
the failure only happens when LDFLAGS contains -flto which says to me
that gcc doesnt parse arguments the same as when executing other
helpers.
LDFLAGS=-flto CPPFLAGS=-DD=\'\"\"\' ./configure
but still not a bash issue
-mike
On Wed, Mar 23, 2011 at 2:51 PM, Ralf Thielow wrote:
> i've found a german misspelling in command "cd".
> Where can i fix it?
please use bug-bash, not bash-announce
a bit odd announce isnt moderated so only people like Chet can announce ...
-mike
On Mon, Mar 28, 2011 at 2:25 PM, Greg Wooledge wrote:
> In any case, I see no benefit to changing how [[ works. A change would
> just cause more confusion.
and probably break many existing scripts
-mike
seems to be just like the bug fixed in bash41-006, but with a diff for loop
style. simple example:
f() {
for (( :; :; )) ; do
cat <
signature.asc
Description: This is a digitally signed message part.
or the delay ... that patch does indeed seem to fix the issue. thanks!
-mike
signature.asc
Description: This is a digitally signed message part.
On Sunday, May 29, 2011 22:18:33 Bradley M. Kuhn wrote:
> It's been two years since this discussion began
and there have been requests older than that. you just found the most
"recent".
-mike
signature.asc
Description: This is a digitally signed message part.
On Saturday, June 18, 2011 16:37:18 John Williams wrote:
> Is this a bash bug, or intentional behavior?
it's coming from the kernel, not bash
post the output of `mount` and make sure that it doesnt have the "noexec" flag
-mike
signature.asc
Description: This is a digitally signed message part.
The fact that bash accepts 'exit -1' and 'exit -- -1', but
> > only 'return -- -1', is the real point that you are complaining about.
>
> That's a reasonable extension to consider for the next release of bash.
i posted a patch for this quite a while
which I'll likely start doing now. ;-)
>
> ... or did I miss something?
i rarely use `history`, so i cant suggest any improvements there
-mike
signature.asc
Description: This is a digitally signed message part.
ke -j y.tab.{c,h}
a correct system would not show the yacc parser running twice :)
simple patch is to have the .h file depend on the .c file, and have the .h file
itself issue a dummy rule (to avoid make thinking things changed).
-mike
--- a/Makefile.in
+++ b/Makefile.in
@@ -579,16 +579,17 @@
these top level files being generated. now the subdirs won't try and
recursively enter the top level.
(noticed by David James)
-mike
--- a/Makefile.in
+++ b/Makefile.in
@@ -597,6 +598,11 @@
# $(YACC) -d $(srcdir)/parse.y
# -if cmp -s old-y.tab.h y.tab.h; then mv old-y.tab.h y
the top level Makefile will recurse into the defdir for multiple targets
(libbuiltins.a, common.o, bashgetopt.o, builtext.h), and since these do not
have any declared interdependencies, parallel makes will recurse into the
subdir and build the respective targets.
nothing depends on common.o or bas
pting the files will make things harder, but won't make
it inaccessible to people who really want it.
if you want to protect private information, don't put it on a remote server.
-mike
signature.asc
Description: This is a digitally signed message part.
set -- "$@" a b c
to add items to the start:
set -- a b c "$@"
to extract slices:
set -- "${@:[:]}"
e.g.
set -- a b c
set -- "${@:2:1}" # this sets $@ to (b)
with those basics, you should be able to fully manipulate $@
-mike
signature.asc
Description: This is a digitally signed message part.
at ? if you want someone else to take
care of the details, i can help ... i've converted a bunch of projects in the
past over to git from CVS/SVN.
-mike
signature.asc
Description: This is a digitally signed message part.
On Friday 25 November 2011 22:28:49 Chet Ramey wrote:
> On 11/24/11 12:36 PM, Mike Frysinger wrote:
> > On Wednesday 23 November 2011 23:23:43 Chet Ramey wrote:
> >> I spent a little while messing around with git over the past couple of
> >> days, and ended up updating
On Sunday 27 November 2011 21:31:16 Chet Ramey wrote:
> On 11/26/11 2:56 AM, Mike Frysinger wrote:
> >> Thanks. I have bash sources going back a number of years, and I can get
> >> them into git. It will just take me a while.
> >>
> >> The question
ack empty
1
as does your popall func
-mike
signature.asc
Description: This is a digitally signed message part.
(/bin/bash) ?
because you grepped your own script named "crond.sh"
make the awk script smarter, or use pgrep
-mike
signature.asc
Description: This is a digitally signed message part.
lQaVF5 | openssl base64 -d; echo
$ out=$(echo OHBjcWNLNGlQaVF5 | openssl base64 -d); echo "${out}"
... many other ways ...
-mike
signature.asc
Description: This is a digitally signed message part.
can't tell if this is a bug or a feature.
FOO= BAR=bar
: ${FOO:=${BAR}
echo $FOO
i'd expect an error, or FOO to contain those excess braces. instead, FOO is
just "bar".
-mike
signature.asc
Description: This is a digitally signed message part.
r both sh(1) and for
> > execlp(2) and friends.
>
> Is it that you don't read english as a first language, or are you just
> trying to be argumentative?'
i'm guessing irony is lost on you
ad hominem attacks have no business on this list or any other project. if you
On Tuesday 20 March 2012 15:55:18 Chet Ramey wrote:
> or the even simpler
>
> f()
> {
> f | f &
>
> }
> f
i like the variant that uses ":" instead of "f":
:(){ :|:& };:
-mike
signature.asc
Description: This is a digitally signed message part.
cial Patch 24, Chet Ramey, 2012/03/12
Bash-4.2 Official Patch 23, Chet Ramey, 2012/03/12
Bash-4.2 Official Patch 22, Chet Ramey, 2012/03/12
Bash-4.2 Official Patch 21, Chet Ramey, 2012/03/12
-mike
signature.asc
Description: This is a digitally signed message part.
On Saturday 07 April 2012 16:45:55 Linda Walsh wrote:
> Is it an accidental omission from the bash manpage?
it's in the man page. read the "Arithmetic Expansion" section.
-mike
signature.asc
Description: This is a digitally signed message part.
. 4.2_p24 (just what i have locally):
aaaäöü aaaäöü aaaäöü
seems like a bug to me
-mike
signature.asc
Description: This is a digitally signed message part.
if you disable readline, the complete.def code fails to build. simple patch
below (not sure if it's correct, but at least gets the conversation going).
-mike
--- a/builtins/complete.def
+++ b/builtins/complete.def
@@ -49,6 +49,8 @@ $END
#include
+#ifdef READLINE
+
#include
#in
On Monday 23 April 2012 18:57:05 Chet Ramey wrote:
> On 4/23/12 12:22 AM, Mike Frysinger wrote:
> > if you disable readline, the complete.def code fails to build. simple
> > patch below (not sure if it's correct, but at least gets the
> > conversation going).
>
&
On Monday 23 April 2012 20:08:26 Chet Ramey wrote:
> On 4/23/12 7:40 PM, Mike Frysinger wrote:
> > On Monday 23 April 2012 18:57:05 Chet Ramey wrote:
> >> On 4/23/12 12:22 AM, Mike Frysinger wrote:
> >>> if you disable readline, the complete.def code fails to build.
On Tuesday 24 April 2012 08:23:04 Chet Ramey wrote:
> On 4/24/12 12:00 AM, Mike Frysinger wrote:
> >> OK, so you've stripped the local readline copy out of the source tree?
> >
> > yes
> >
> >> Then configured it to build with a system readli
1 - 100 of 524 matches
Mail list logo
