On Wed, Feb 23, 2022 at 03:37:12PM -0500, Chet Ramey wrote:
> As others have noted, bash-completion is a separate package.
> But we might be able to figure out where it's not being appropriately
> quoted if you enable `set -x' before attempting the completion. At
> least that would give you a backt
On 2/23/22 11:34 AM, Ian! D. Allen wrote:
> Bash Version: 5.0
> Patch Level: 17
> Release Status: release
>
> Description:
> BASH completion cannot correctly handle file names containing newline
> characters.
As others have noted, bash-completion is a separate package.
But we might be ab
On Wed, 23 Feb 2022 11:34:52 -0500
"Ian! D. Allen" wrote:
> # Now, load the completion scripts and watch it break:
> bash-5.0$ source /usr/share/bash-completion/bash_completion
Issues regarding completion scripts should be reported to their respective
authors, such as https://github
besides not running newest bash
On Wed, Feb 23, 2022, 17:36 Ian! D. Allen wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2
> -fdebug-prefix-map=/build/bash-a6qmCk/bash-5.0=. -fstack-protect
as far i know is the bash compl external and buggy
i trash it since 2002
On Wed, Feb 23, 2022, 17:36 Ian! D. Allen wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2
> -fdebug-prefix-map=/bui
On 7/2/21 2:13 AM, Phi Debian wrote:
Thanx Chet for taking time to explain.
May be readline API should have a way to know that a quote ['"`] is opened
ine many previous lines and the first occurence of such quote ine the
current one , is a closing one.
There might be a way to do it using the
Thanx Chet for taking time to explain.
May be readline API should have a way to know that a quote ['"`] is opened
ine many previous lines and the first occurence of such quote ine the
current one , is a closing one.
Well I guess this is too much of a trouble for something living this way
for such
On 6/22/21 3:52 AM, Phi Debian wrote:
When doing
$ echo foo "bar" /tm
I got /tm expanded to /tmp/ that is indeed correct.
But if I do
$ echo foo "bar
more bar" /tm
No completion is done. My question is doest this behavior a feature or a
bug?
Neither, really, it's just a consequence of rea
May be posting a link is not appropriate so I cut/paste it here
I bumped into this problem regarding bash completion, can't find reference
to it.
When doing
$ echo foo "bar" /tm
I got /tm expanded to /tmp/ that is indeed correct.
But if I do
$ echo foo "bar
more bar" /tm
No completion is don
On 3/26/19 3:43 AM, d3fault wrote:
> Bash Version: 4.4
> Patch Level: 12
> Release Status: release
>
> Description:
> In the following example it auto-completes without putting double
> quotes around "hi mom", which means a process would see it as 2
> separate args instead of 1.
If you wan
On 2/20/18 3:15 PM, Justin Pryzby wrote:
> Bash Version: 4.1
> Patch Level: 2
> Release Status: release
>
> Description:
> SIGABRT during readline completion.
>
> Repeat-By:
> Unable to reproduce
It's likely that this has been fixed in the eight years since bash-4.1 was
released
On 8/22/16 9:43 AM, Jaro Punta wrote:
> I am not sure this is a bug but I cannot find an explanation why this
> happens. Sometimes when I execute certain commands, and I press the
> Tab key while I am typing the command, then after the commands
> finishes, the terminal is left in a abnormal state (
On 8/24/15 4:01 PM, Neven Sajko wrote:
> Hi,
>
> I use bash 4.3.039 and there is a bug (not necessarily a recent
> regression) with its file name completion feature.
> for example I have this in shell input:
> db.rc $home/Downloads/games/DOS/Captai
> and after I press Tab I have this:
> db.rc
> for example I have this in shell input:
> db.rc $home/Downloads/games/DOS/Captai
> and after I press Tab I have this:
> db.rc \$home/Downloads/games/DOS/Captain\ Bible\ in\ the\ Dome\ of\
> Darkness.zip
Sorry, the completed command line was wrapped:
db.rc \$home/Downloads/games/DOS/Captain\
Chris F.A. Johnson wrote:
>I can confirm it on 3.05b, 3.0 and 4.2:
>
> while [ ${n:=0} -lt 5 ]
> do
> se
>
> All I get is a beep.
Hmm... It is still completing. But not command completion. It is
doing filename completion instead of command completion. It is out of
sync with the current
On Sat, 5 Nov 2011, Bob Proulx wrote:
Peng Yu wrote:
Current, bash doesn't do command completion between do and done (for loop).
I'm wondering if this feature can be added.
Of course bash does do command completion between do and done. Can
you give an exact example test case? On what versio
Peng Yu wrote:
> Current, bash doesn't do command completion between do and done (for loop).
> I'm wondering if this feature can be added.
Of course bash does do command completion between do and done. Can
you give an exact example test case? On what version of bash?
Bob
Le mardi 09 août 2011 à 10:05 +0800, Clark J. Wang a écrit :
> On Sun, Aug 7, 2011 at 11:35 PM, jonathan MERCIER
> wrote:
> I have a bash completion file (see below)
> It works fine, but i would like add a feature => not expand
> the flag by
> a space when it contai
On Sun, Aug 7, 2011 at 11:35 PM, jonathan MERCIER
wrote:
> I have a bash completion file (see below)
> It works fine, but i would like add a feature => not expand the flag by
> a space when it contain '='
> curently when i do:
> $ ldc2 -Df
> ldc2 -Df=⊔
> i would like:
> ldc2 -Df
> ldc2 -Df=
>
> w
Benjamin Rutt <[EMAIL PROTECTED]> writes:
> I have an animated gif that shows the bug. If you browse to:
>
> http://bmi.osu.edu/~rutt/bashcompletion.gif
>
> it will show how e.g.
>
> cd $HOM
>
> will expand to
>
> cd \$HOME
>
> I think this is a bug in the method:
>
> _cd()
> {
> local IFS=
Christian Boltz wrote:
> Hello,
>
> I've found a bug in bash autocompletion...
>
>
> Configuration Information [Automatically generated, do not change]:
> Machine: i586
> OS: linux
> Compiler: gcc -I/usr/src/packages/BUILD/bash-3.0
> -L/usr/src/packages/BUILD/bash-3.0/../readline-5.0
> Compilat
> Why not just add a mount for C: as /c?
>
> That's what I did, so now I can move around with ease, with the same
> number of characters to have to type as c:
Hm, yes that is a nice alternate solution. Thanks for the idea!
___
Bug-bash mailing list
B
Gary Fritz <[EMAIL PROTECTED]> writes:
> In
> http://groups-
> beta.google.com/group/gnu.bash.bug/browse_thread/thread/e0dc6716afe8162d/df
> a06fd85db708e1
> a bug was reported that prevented TAB completion from working properly in
> Cygwin when the "c:/" synonym for "/cygdrive/c" was used. Beca
Chet Ramey <[EMAIL PROTECTED]> wrote:
> The fix, available in the current release of bash, is to modify the
> contents of the COMP_WORDBREAKS variable to remove the `:'.
Outstanding!! Exactly what I needed. Thanks!
Gary
___
Bug-bash mailing list
Bug
Gary Fritz wrote:
> In
> http://groups-
> beta.google.com/group/gnu.bash.bug/browse_thread/thread/e0dc6716afe8162d/df
> a06fd85db708e1
> a bug was reported that prevented TAB completion from working properly in
> Cygwin when the "c:/" synonym for "/cygdrive/c" was used. Because ":" is
> consider
25 matches
Mail list logo
