On Wed, Jan 9, 2019 at 10:54 PM Jeremy wrote:
(...)
> 3.2.57(1)-release (x86_64-apple-darwin15)
>
>
> This is on MacOS 10.11.6. If there is a better place for me to report this
> bug, please let me know.
Have you tried the latest version? Bash 5.0 was just released:
Configuration Information [Automatically generated, do not change]:
Machine: Mac
OS: Darwin
Compiler: gcc
Compilation CFLAGS: Xcode
uname output: Darwin Octo.local 15.6.0 Darwin Kernel Version 15.6.0: Thu
Jun 21\
20:07:40 PDT 2018; root:xnu-3248.73.11~1/RELEASE_X86_64 x86_64
Machine Type:
Configuration Information [Automatically generated, do not change]:
Machine: Mac
OS: Darwin
Compiler: gcc
Compilation CFLAGS: Xcode
uname output: Darwin Octo.local 15.6.0 Darwin Kernel Version 15.6.0: Thu
Jun 21\
20:07:40 PDT 2018; root:xnu-3248.73.11~1/RELEASE_X86_64 x86_64
Machine Type:
Yes, certainly. I've also minimized the .bashrc and .bash_profile in here to
what will also reproduce. Running "foo" here will peg my CPU down.
zrak:~ synthmeat$ alias; declare -f
alias foo=' echo "bar" '
shell_session_delete_expired ()
{
if ( [ ! -e
Seems like if there's "complete -D" defined then "progcomp_alias" would
never work. So does it make more sense to make "progcomp_alias" has higher
priority than "complete -D"?
On 1/9/19 2:39 PM, Daniel Colascione wrote:
> Any chance we can revive this patch now that Bash 5 is out? (The patch
> itself, of course, would need to be rebased.)
Yes, I plan to.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' -
On 1/9/19 2:27 PM, kevin wrote:
> My message was poorly formatted (I lack of experience) and consequently you
> misunderstood it.
> The shell operation is unusual when a regular expression appears inside a
> conditional expression. Indeed, neither the Bash man page or the Bash
> Reference Manual
Any chance we can revive this patch now that Bash 5 is out? (The patch
itself, of course, would need to be rebased.)
On Fri, Jun 8, 2018 at 9:27 AM Chet Ramey wrote:
>
> On 6/7/18 10:45 PM, Daniel Colascione wrote:
> > Hey. I'd appreciate a quick peek at this patch. The lack of visual feedback
>
On Wed, Jan 9, 2019 at 4:59 AM Ante Perić wrote:
(...)
> Description:
> Having an alias of type:
> alias bug="\
>echo \"no output, 100% cpu\" \
> "
> in .bashrc will give no output, will not complete, and it will peg the CPU to
> 100%.
Can you share the output of (right
On 1/9/19 1:24 AM, Ante Perić wrote:
> Bash Version: 5.0
> Patch Level: 0
> Release Status: release
>
> Description:
> Having an alias of type:
> alias bug="\
>echo \"no output, 100% cpu\" \
> "
> in .bashrc will give no output, will not complete, and it will peg the CPU to
On 1/8/19 3:50 PM, a...@freakout.de wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -fstack-protector -Wno-parentheses -Wno-format-security
> uname output: Linux bongo 2.6.32-042stab134.8 #1 SMP Fri
On Wed, Jan 9, 2019 at 3:04 PM Chet Ramey wrote:
>
> On 1/9/19 4:11 AM, Tadeus Prastowo wrote:
> > Hi Chet,
> >
> > It seems to me that Bash does not require copyright assignment for
> > contributed patches, unlike GCC and Emacs. Is that true?
>
> I rarely get patches longer than a few lines, so
On 1/9/19 4:11 AM, Tadeus Prastowo wrote:
> Hi Chet,
>
> It seems to me that Bash does not require copyright assignment for
> contributed patches, unlike GCC and Emacs. Is that true?
I rarely get patches longer than a few lines, so I don't consider it
a problem. Do you think it's an issue?
--
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin18.2.0
Compiler: clang
Compilation CFLAGS: -DSSH_SOURCE_BASHRC -Wno-parentheses -Wno-format-security
uname output: Darwin zrak 18.2.0 Darwin Kernel Version 18.2.0: Mon Nov 12
20:24:46 PST 2018;
14 matches
Mail list logo
