hi,
I do not think it is a bug; jobs.c:
1607/* We need to add a CR only if this is an interactive shell, and
1608 we're reporting the status of a completed job asynchronously.
1609 We can't really check whether this particular job is being
1610 reported asynchronously, so j
On 11/13/2014 11:25 PM, yutingkao23@yutingkao23-desktop wrote:
> Does bash-3.1 with patch 23 fix the CVE-2014-7187 already ?
Yes. Read the list archives. You are running a bogus test (and should
report it to whoever wrote it), as the test you are running is NOT a
test for the CVE vulnera
On 11/14/14, 1:25 AM, yutingkao23@yutingkao23-desktop wrote:
> Bash Version: 3.1
> Patch Level: 23
> Release Status: release
>
> Description:
> Where I test `(for x in {1..200} ; do echo "for x$x in ; do :"; done;
> for x in {1..200} ; do echo done ; done) | bas$
> It shows
>
> I'm working on adding tab completion to an application that deals with
> URLs, among other things. Since readline includes ':' as a delimiting
> character, it causes minor annoyances with tab-completing URLs. There's the
> known workaround of removing ':' from COMP_WORDBREAKS, but that requires
>
On 11/13/14, 2:21 PM, idal...@idallen.ca 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='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
Thanks for the reply Chet,
The completer is being setup in Bash, not directly through readline (sorry
if I wasn't detailed enough in my original post).
Even though readline might break the completion on the ':', we can use
COMP_LINE/COMP_POINT to figure out the URL that needs to be completed
(igno
Hi,
I would like to propose a patch, that allows to use \o in prompt:
$ PS1="(\o)\u@\h \w $ "
(himBH)merlin@ ~/bash $ set +hm
(iBH)merlin@ ~/bash $
\o gets replaced by all options that are on and visible via set -o.
do you think it can be useful? (I hope this feature is not already
so
On Fri, Nov 14, 2014 at 06:01:37PM +0100, Piotr Grzybowski wrote:
> I would like to propose a patch, that allows to use \o in prompt:
>
> $ PS1="(\o)\u@\h \w $ "
> (himBH)merlin@ ~/bash $ set +hm
> (iBH)merlin@ ~/bash $
>
> \o gets replaced by all options that are on and visible via set
thanks.
hah. I knew it. forget the previous mail. Consider it just an
academical discussion ;-)
cheers,
pg
On Fri, Nov 14, 2014 at 6:04 PM, Greg Wooledge wrote:
> On Fri, Nov 14, 2014 at 06:01:37PM +0100, Piotr Grzybowski wrote:
>> I would like to propose a patch, that allows to use \o in pr
On Fri, Nov 14, 2014 at 10:30:12AM -0500, Chet Ramey wrote:
> Yes, it's intended. Piotr identified the code that does this. If the
> shell is currently interactive, it can't be sure under what circumstances
> it's printing a job notification.
If the shell is printing the job notification because
On 11/14/14, 10:49 AM, Vadim Berezniker wrote:
> Thanks for the reply Chet,
>
> The completer is being setup in Bash, not directly through readline (sorry
> if I wasn't detailed enough in my original post).
> Even though readline might break the completion on the ':', we can use
> COMP_LINE/COMP_P
Hi, why does not the sort processes by priority? This is a bug or not?
I attached a screenshot with a problem.
I use VMware Workstation and Ubuntu 14.04 LTS
Best regards,
Artem Y.
On Fri Nov 14 2014 at 2:47:04 PM Chet Ramey wrote:
> On 11/14/14, 10:49 AM, Vadim Berezniker wrote:
> > Thanks for the reply Chet,
> >
> > The completer is being setup in Bash, not directly through readline
> (sorry
> > if I wasn't detailed enough in my original post).
> > Even though readline mi
Artem Yegorov wrote:
> Hi, why does not the sort processes by priority? This is a bug or not?
> I attached a screenshot with a problem.
> I use VMware Workstation and Ubuntu 14.04 LTS
You seem to have confused the 'ps' command with 'bash' and reported
something that you think should be different a
14 matches
Mail list logo
