Apparently bad checksums in tcpdump/wireshark captures for outgoing
traffic are normal, when hardware offload is enabled. The NIC only
fills in the correct value after data has been copied to the NIC, which
is after capture takes a snapshot of the buffer with whatever garbage
was there. See the l
Public bug reported:
While playing a video with mpv, X locked up entirely (not even mouse
movement did anything). Even kill -9 won't kill the X server, although
/etc/init.d/sddm restart did get the video card to text mode. (But the
Xorg process is stuck in state D.) Unfortunately this means I c
** Attachment added: "Nothing interesting"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1602097/+attachment/4699113/+files/Xorg.0.log
** Description changed:
While playing a video with mpv, X locked up entirely (not even mouse
movement did anything). Even kill -9
** Attachment added: "full dmesg output, including kernel hung-task stack
traces"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1602097/+attachment/4699112/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
When installing 1.3.99-1-1 on Ubuntu 15.10 (AMD64), I get the following
error while the package configures itself:
```
libdvd-pkg: Checking orig.tar integrity...
/usr/src/libdvd-pkg/libdvdcss_1.3.99.orig.tar.bz2: OK
libdvd-pkg: Unpacking and configuring...
libdvd-pkg: Buildin
Public bug reported:
My system boots from XFS on RAID10 on GPT partitions (no LVM). The
RAID10 uses the "far2" layout, and has three component devices. I use
grub-pc for non-EFI booting, because this system is old and doesn't
support EFI (Intel DG965WH from 2008).
I added a fourth hard drive an
Public bug reported:
As per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787950,
/usr/share/mdadm/checkarray fails when it tries to read
/sys/block/mdX/md/sync_action, if running under dash (or apparently most
shells other than bash), with a 4.x kernel.
Present in Ubuntu 15.10, where a defau
If you want full-featured vim in a terminal, install vim-gtk and run it
as "vim".
It only opens a new window if you run it as gvim, or vim -g.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/837882
Tit
Public bug reported:
kwin on open source drivers on a 1GB Radeon HD6870 (BARTS core) starts
off using a lot of memory, and uses more and more until it can't
allocate textures and you get black rectangles instead of windows
sometimes. kill/restart kwin_x11 gets back to the same state as on
login.
** Package changed: grub-installer (Ubuntu) => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445156
Title:
Ubiquity grub-install fails when installing to a RAID10 with manual
pa
** Description changed:
+ edit: derp, of course this fails, mdadm isn't installed until you chroot
+ in and do that manually. I wasn't thinking when I reported this >.<.
+ See http://askubuntu.com/questions/505446/how-to-install-ubuntu-14-04
+ -with-raid-1-using-desktop-installer for details on h
Public bug reported:
Ubiquity running from Kubuntu 15.04 beta2 usb image.
The installer GUI said it was going to try installing GRUB on sda, not
sda1. (This isn't a duplicate of #1322182)
my setup is:
/ on XFS on /dev/md0: RAID10 of sda2,sdb2,sdc2
/home on XFS on a different md RAID10 of sda3,s
This bug is back, present in
xubuntu-daily-live-20150416-vivid-desktop-amd64.iso
but not in xubuntu-daily-live-20150414-vivid-desktop-amd64.iso from 2
days earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
I just wanted a simple proxy, so I ran
tcpwatch-httpproxy -p 10.0.0.19:8080 -s > /dev/null
(On a machine that also has a real IP)
Then I started some downloads running from another computer, and later
noticed tcpwatch-httpproxy was using 1.6GB of RAM. That might be the
full
Public bug reported:
Even after rm -r ~/.subcommander, subcommander still 2.0 beta5
(Ubuntu 14.10) still crashes when I try to do pretty much anything.
e.g. run subcommander, right click on the "Subcommander" project. "New
repository" in the dropdown -> segfault.
I wasn't able to get it to d
This will get fixed upstream at some point for sure, so having the bug
here is probably only useful as a reminder to check that we have an
updated-enough GRUB before the next release, or next LTS release at
worst.
** Description changed:
Filing a note here in case I forget later.
It looks
** Description changed:
Filing a note here in case I forget later.
- It looks like GRUB in 14.10 doesn't support XFS's new on-disk metadata
- format that has CRCs. (rationale:
+ It looks like GRUB (2.02-beta2-15) in 14.10 doesn't support XFS's new
+ on-disk metadata format that has CRCs. (r
Public bug reported:
Filing a note here in case I forget later.
It looks like GRUB (2.02-beta2-15) in 14.10 doesn't support XFS's new
on-disk metadata format that has CRCs. (rationale:
https://www.kernel.org/doc/Documentation/filesystems/xfs-self-
describing-metadata.txt)
mkfs.xfs -m crc=1,fino
Is this still the case? Natty is ancient. I thought grub1 had learned
how to deal with Linux XFS. (maybe with fsync and then FIEMAP, or the
xfs-specific ioctl that xfs_bmap -vpl some_file uses. (output is
similar to filefrag -e, but shows you when there's a hole, instead of
leaving it up to t
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/775507
Title:
grub2 in natty fails to read xfs files
To manage notifications about this
Public bug reported:
14.04 -> 14.10 went flawlessly, on my nearly-default-install laptop.
The only problem I noticed was when prompted to yN or d for details.
After hitting d, return, then exitting from less (without doing anything
weird like ^z), the prompt for what to do next wasn't printed. I
Formatting ate the multiple blank lines. There is a blank line for
every time I pressed return, before N.
pasted to a file, too, in case anyone didn't fully understand the
description.
** Attachment added: "output.txt"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1
> Sorry for not getting back earlier.
No worries. Glad you got your systems sorted.
Not closing this bug, because your problem wasn't this bug after all..
>.< I still want to leave this bug here for the purpose I editted the
OP to.
> Nonetheless I'd like to know if there is way to detect if
ba
still can't reproduce. Is there any chance /nfs/AppServer/applics sometimes
looks like a broken symlink? Do you get the same behaviour if you
ln -s /tmp /tmpX
and then do your examples exactly as typed? And ideally, can you do it without
writing to /?
mkdir -p test/tmp; cd test
ln -s ./tmp t
Oh forgot to mention, you can toggle programmable completion on or off with
shopt -u progcomp# unset
shopt -s progcomp# set
Usually bash's builtin file/directory completion gets it right, and
doesn't trip up on unusual characters in filenames (e.g. 'foo*' leads to
problems with progcomp.)
ln -s /tmpX /tmpproduces:
lrwxrwxrwx 1 peter peter 5 Dec 9 11:58 /tmp/tmpX -> /tmpX (a broken symlink)
Did you mean ln -s /tmp /tmpX ?
When cooking up a testcase, it's bad practice to make one that only
works for root.
mkdir -p test/tmp
cd test
ln -s ./tmp tmpX
ls ./tmp[TAB] => tmp/
Found a time when I didn't mind rebooting, and tested tested
linux-image-3.18.0-031800rc7-generic version 3.18.0-031800rc7.201411302035
peter@tesla:~$ uname -a
Linux tesla 3.18.0-031800rc7-generic #201411302035 SMP Mon Dec 1 01:36:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
peter@tesla:~$ route -
$HOME is a good example as a testcase, but a terrible example of it
actually being a problem, because ~/file.txt is easier to type anyway.
$OLDPWD is more annoying. I think progcomp used to expand the variable
on your cmdline, and then of course completion just worked normally. I
think that expa
Public bug reported:
Noticed the bug on trusty, still present in
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/vte3/vivid/view/head:/src/vte.sh
__vte_prompt_command():
"${PWD/#$HOME/~}" needs to be
"${PWD/#$HOME/\~}"
because ${parameter/pattern/string} does tilde expansion on strin
crap, wrong bug, meant to post that last on bug 1173728
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790043
Title:
Bash-completion slows up the start of bash
To manage notifications about this bug
So to be clear, the changes I'm suggesting are:
* /etc/skel/.bashrc (pkg=base-files) change the progcomp check to an
un-commented
# enable programmable completion
[[ -e /etc/profile.d/bash_completion.sh ]] && .
/etc/profile.d/bash_completion.sh
* /etc/bash.bashrc (pkg=bash): remove the progcomp
So to be clear, the changes I'm suggesting are:
* /etc/skel/.bashrc (pkg=base-files) change the progcomp check to an
un-commented
# enable programmable completion
[[ -e /etc/profile.d/bash_completion.sh ]] && .
/etc/profile.d/bash_completion.sh
* /etc/bash.bashrc (pkg=bash): remove the progcomp
As discussed in bug 790043 (about the slowdown of loading completions),
the out-of-the-box configuration seems to be to load programmable
completions (progcomp) for login shells, but not for non-login shells
(e.g. bash in an xterm).
TL:DR summary: ~/.bashrc should source
/etc/profile.d/bash_compl
The shell builtin command return can be used to exit early from a file
sourced with . or source.
bash_completion could protect itself from being re-sourced by doing
type __reassemble_comp_words_by_ref 2>/dev/null && return
Or maybe
complete -p paste 2>/dev/null && return
So complete -r; source /us
bug 1173728 is about programmable completion being loaded by default, or
not. Further discussion about how and whether it is should go there.
Sorry for the tangent about it in this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: casper (Baltix)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/25496
Title:
Unable to boot Ubuntu using TORAM=yes (copy livecd to RAM)
To ma
with 14.04:
time find -name '*.[ch]' | xargs grep -i 'volatile.*s3tc' # en_CA.utf8
real0m44.320s
user0m43.777s
sys 0m0.459s
time find -name '*.[ch]' | LANG=C xargs grep -i 'volatile.*s3tc'
real0m2.078s
user0m1.795s
sys 0m0.381s
time find -name '*.[ch]' | xargs grep 'vola
Does the completed filename look different from the output of ls?
Can you copy/paste a test-case? I don't know how to type cyrillic
characters without busting out gucharmap, but I have no problem pasting
mkdir / touch 'some UTF8' into a shell to test it out.
e.g.
touch cyrillic with spaces
echo
hmm, actually now that dpkg completions are dynamically loaded, you
could do whatever in completions/dpkg without being a burden for every
interactive shell. Might be worth thinking about, but really, just
don't remove dctrl-tools. :P
--
You received this bug notification because you are a membe
** Changed in: bash-completion (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388423
Title:
Please package completions for apt-mark into bash_completion
To
Was working on completions for something else, and thought of this when
I saw completions/make checking if COMPREPLY has only a single entry.
If it does, that means completion will replace the user's word, rather
than show possible completions. In that case, run compopt -o nospace.
And maybe als
Attached the full-fledged perl script I cooked up to investigate
obsolete conffiles.
grep the output, it doesn't take options.
When removing them, it often leaves empty directories, so don't forget
to remove them, too. (If they aren't owned by some other package...
check with dlocate, or add sup
@Atanas: interesting idea to have bash load completions in the
background, but shell scripting as a language has NO support for doing
anything like this. You can't just have it happen in another thread,
because you need it to modify the context of the CURRENT shell.
You'd need a new major featu
/etc/profile.d/bash_completion.sh only sources /usr/share/bash-
completion/bash_completion if it hasn't been already. note the check on
-z "$BASH_COMPLETION_COMPAT_DIR", which the giant bash_completion script
defines with
: ${BASH_COMPLETION_COMPAT_DIR:=/etc/bash_completion.d}
readonly BASH_COMPL
attaching a patch. I think I tested everything I changed. I replaced
the loop over ls output with grep -l | sed.
I made a bunch of overall changes and improvements to the script, too.
When completing an empty word, instead of returning the full list of all
available packages, all PIDs, and all
submitted upstream:
https://alioth.debian.org/tracker/index.php?func=detail&aid=314899&group_id=100114&atid=413095
_install_xspec '!.@(wxm?(x)|mac)' wxmaxima
is all it takes these days, prob. don't want to make a separate file.
** Bug watch added: alioth.debian.org/ #314899
http://alioth.debi
submitted upstream as
https://alioth.debian.org/tracker/index.php?func=detail&aid=314898&group_id=100114&atid=413095
** Bug watch added: alioth.debian.org/ #314898
http://alioth.debian.org/support/tracker.php?aid=314898
--
You received this bug notification because you are a member of Ubuntu
It's done the way it is to save RAM and startup time for every
interactive bash. If bash had to store both versions of a function, and
pick at runtime, it would be slightly slower every completion, and more
importantly, slightly slower to load.
As I understand it, this is the design tradeoff tha
looks like this has been submitted upstream by someone:
https://alioth.debian.org/tracker/index.php?func=detail&aid=314875&group_id=100114&atid=413095
Didn't check if it was the same script or not.
** Bug watch added: alioth.debian.org/ #314875
http://alioth.debian.org/support/tracker.php?aid
Good catch, but the right fix is to use command grep, like most of the uses of
grep in bash-completion do. --color=never isn't portable to systems where grep
isn't GNU grep. So yes, this is a bug, and bash-completion is supposed to not
break even if you have
alias grep='cat /dev/random'
But
This is already fixed upstream in git head.
** Changed in: bash-completion (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330173
Title:
bash-completion o
This isn't bash-completion's bug. If anything, it's bash's bug, if
you're sure that COMPREPLY is being mishandled.
More likely, it's a bug in your own script, since the usual programmable
completion code jumps through some hoops do to the Right Thing for files
and directories. Your script has hu
or I can get it to give errors with
eg pull [TAB]
it bash: [: 2: unary operator expected and tacks origin onto the end of the
command line.
origin
On Trusty, with git 2:2.1.3-1avh1~tru from the git PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Now it isn't throwing errors, but it doesn't filter the possible
completions to ones that match what's already typed.
** Summary changed:
- bash-completion of filename does not work 100% (unlike git) - gives ": 1:
unary operator expected" error
+ bash-completion of filename doesn't restrict com
*** This bug is a duplicate of bug 1079641 ***
https://bugs.launchpad.net/bugs/1079641
** This bug has been marked a duplicate of bug 1079641
bash-completion errors and problems (e.g. not restricting completions to
matching current word)
--
You received this bug notification because you
** Changed in: bash-completion (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372286
Title:
unwanted space after directory completion (probably old cr
There's something fishy going on,
/usr/bin/python /etc/ba[TAB] => prints a single completion, but doesn't apply
it.
bash_completion.d/
python /etc/ba[TAB] => /etc/bash_completion.d/
I think when testing this before, I had my completion dynamic loading
messed up, and wasn't getting /usr/share/
oh, I am using git 2:2.1.3-1avh1~tru, from the git PPA, not trusty's,
but at least that means its fixed upstream and will roll out eventually,
whether or not trusty has it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
update: be careful with obsolete conffiles. The same file can be
obsolete in one package, but still be provided and non-obsolete in
another package. e.g. I removed my /etc/bash_completion.d/mercurial,
since my script found it, but it had moved from mercurial to mercurial-
common, and is listed no
Not seeing this in Trusty. Reopen if I made a mistake, but I think I
have just the Trusty-shipped completions loaded in the shell I tested
with, not my fixed version.
If you do see it, it might be from old cruft in /etc/bash_completion.d/.
report anything that needs to be blacklisted to bug 13722
*** This bug is a duplicate of bug 1188897 ***
https://bugs.launchpad.net/bugs/1188897
** This bug has been marked a duplicate of bug 1188897
Completion for "service" only looks up /etc/init.d/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Oh, this is supported and documented in a .txt that the .deb doesn't
ship.
simply put
COMP_FILEDIR_FALLBACK=1
in your ~/.bash_completion (or ~/.bashrc)
doc/bash_completion.txt in the source tree.
https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=bash-
completion/bash-
completion.git;
You have alias ls='ls -F', and /etc/bash_completion.d/apport_completion
fails to use command ls to avoid getting your alias.
/etc/bash_completion.d/apport_completion is supplied by apport, so it's
a bug in that package.
working on a patch now.
** Package changed: bash-completion (Ubuntu) => a
I don't have eg installed, but I got the completions from the .deb, and
sourced them in a shell.
Works for me on Trusty; I don't see those error messages. I am using
git from the ppa, though: 2:2.1.3-1avh1~trusty1 not Trusty's 1:1.9.1-1.
(eg uses git's completion functions, and /usr/share/bash-
c
Is this still the case that a default install of Ubuntu doesn't enable
programmable completion out of the box? Not much point making bash-
completion a standard-priority package if it's not enabled by default.
my /etc/bash.bashrc still has the lines
# if [ -f /usr/share/bash-completion/bash_com
** Summary changed:
- bash autocomplete doesn't work with sudo on Ubuntu 13.04
+ bash programmable completion not loaded by default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173728
Title:
bash
adding
COMPREPLY+=( $( initctl list 2>/dev/null | cut -d' ' -f1 ) )
to _services() does the trick.
submitted upstream
https://alioth.debian.org/tracker/index.php?func=detail&aid=314897&group_id=100114&atid=413095
** Bug watch added: alioth.debian.org/ #314897
http://alioth.debian.org/su
I always scroll pages of completion results with space, not enter. I
didn't know enter was an option there. I just tried it, looks like
enter goes by lines, instead of pages? No wonder you were holding it
down. So... don't do that. esp. not on sudo.
To easily get a big list that you need to
** Changed in: bash-completion (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887529
Title:
Option --command-fd no longer present in dpkg but shows
upstream still has a naive _parse_help based handler for ssh-add :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/376546
Title:
Identity filename completion for ssh-add would be nice
To manage noti
** Changed in: bash-completion (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004225
Title:
dramatic combination of apt-get and bash completion
To manage noti
** Summary changed:
- incorrect bash-completion for sudo
+ command / directory mixup for completion of args to meta-commands like sudo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1095180
Title:
c
In Trusty, ping is handled by _ping, so custom code just for ping.
host just gets the generic _minimal.
completion for host was removed in commit
bd482ca2f221323aa461ca75c9457ec11f43570e
host, nslookup: Remove completions for bind utils from
bash_completion.
This fixes tests on systems wit
Works now, in Trusty. Must have finally made it in.
** Changed in: bash-completion (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924676
Title:
Make
** Changed in: bash-completion (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/724244
Title:
"aptitude versions" missing
To manage notifications abou
upstream
https://alioth.debian.org/tracker/index.php?func=detail&aid=314896&group_id=100114&atid=413095
Patch attached there. Also fixes
ls --directory --[TAB] => now completes options
rather than deciding that it's right and user is wrong, and only
accepting a directory name. Not smart for
fixed it:
echo ' -r, --recursive like --directories=recurse' | sed -ne
's/\([^-]\|-[^-]\)*\(--[-A-Za-z0-9]\{1,\}=\{0,1\}\).*/\2/p'
--recursive
using \([^-]\|-[^-]\)* instead of .* at the front of the pattern makes the
greedy match at the front stop at the first --. If there are commands that
bash_completion uses
sed -ne 's/.*\(--[-A-Za-z0-9]\{1,\}=\{0,1\}\).*/\1/p'
to parse the options out of the --help output for MANY commands, including grep.
Unfortunately, it trips up on lines like this from grep:
-r, --recursive like --directories=recurse
because the .* matches right
** Changed in: bash-completion (Ubuntu)
Status: New => Confirmed
** Tags removed: i386 running-unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061114
Title:
Completion suggests rsync --
Input/output error? Normally you only see that when a system call
returns EIO, which usually only happens when your hard drive has an
actual error. (i.e. hard drive failure, not just file that doesn't
exist.)
I think it's unlikely that dpkg would print "Input/output error" when
it didn't see an
This is upstream
https://alioth.debian.org/tracker/index.php?func=detail&aid=311399&group_id=100114&atid=413095
As the comments there show, fixing this is hard, and means you can't
even use compgen. (compgen uses newline as its output record
separator.)
** Changed in: bash-completion (Ubuntu)
** Changed in: bash-completion (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675987
Title:
Add auto-complete support for various office file format
Anything that completes on package names is potentially going to be
slow, because esp. on the first run.
some dpkg and apt commands are slow when the binaries and the data they
need all have to get loaded from disk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
just saw Steve's earlier comment, apparently the logic to pick the right
unistd_32.h or unistd_64.h was added after that, so this is Fix
Released, not Invalid.
There's now asm/unistd_x32.h as well. AFAICT from poking around in the
kernel source, uname -m should return x86_64 when called from a x8
IDK how this got added to bash-completion. It's already an arch:all
binary package, since it's just shell code.
Ah, I see. False positive from Steve's text search that found:
completions/strace:done 2>/dev/null <
/usr/include/asm/unistd.h
./completions/strace:
related: upstream
https://alioth.debian.org/tracker/index.php?func=detail&aid=314895&group_id=100114&atid=413095
Which I opened to report the fact that completion inside either kind of
command substitution is broken, even when not spewing errors.
** Bug watch added: alioth.debian.org/ #314895
Is this still a problem? I don't see anything wrong with completion for
vi / vim. bash_completion ships with
_install_xspec
'*.@(o|so|so.!(conf|*/*)|a|[rs]pm|gif|jp?(e)g|mp3|mp?(e)g|avi|asf|ogg|class)'
vi vim gvim rvim view rview rgvim rgview gview emacs xemacs sxemacs kate
kwrite
The xspec is
works for me on trusty. I don't have lilypond installed, but lilypond
completion is in the main bash_completion script now, so I can test it.
** Changed in: bash-completion (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs
btrfs-tools could ship the contributed completions just as easily, and
install them with dh_bash-completion.
See /share/doc/bash-completion/README.Debian
** Also affects: btrfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 890913 ***
https://bugs.launchpad.net/bugs/890913
** This bug has been marked a duplicate of bug 890913
Typing "prg $HOME/" expands to "prg \$HOME/"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
*** This bug is a duplicate of bug 890913 ***
https://bugs.launchpad.net/bugs/890913
** This bug has been marked a duplicate of bug 890913
Typing "prg $HOME/" expands to "prg \$HOME/"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
This is 2 separate bugs:
1: yeah, jar completion seems to be broken for jar uf foo.jar ...
2: yeah, completion of args inside command substitution is broken, if you mean
that
cvs -d `cat filenam[TAB] => nothing
This is related to bug 1312243, but it's sort of different. I filed upstream
htt
If this wasn't /etc/bash_completion.d/acroread.sh (which is now
blacklisted), then add info to bug 1372286. If we can find more
problematic files to blacklist, we can prevent this problem for other
people.
Closing this because it was reported against a version before the
acroread blacklist was ad
If this wasn't /etc/bash_completion.d/acroread.sh (which is now
blacklisted), then add info to bug 1372286. If we can file more
problematic files to blacklist, we can prevent this problem for other
people.
Closing this because it was reported against a version before the
acroread blacklist was a
** Changed in: bash-completion (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162637
Title:
command completion
To manage notifications about this bug g
** Summary changed:
- Tab key not showing possible files
+ jar uf foo.jar xx/yy/zz.class not completing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070250
Title:
jar uf foo.jar xx/yy/zz.class n
Trusty blacklists acroread.sh from bash_completion.d, so does upstream.
If you still have this on Trusty, bug 1372286 needs to know what other
files to blacklist to un-break completion.
Good testcase and description of exactly what the bug is, copied it for
1372286.
** Changed in: bash-completi
If we can figure out if there's one bad file that is commonly left lying
around, and breaks things, a workaround can be shipped in bash-
completion to blacklist it.
I'm going to close any pre-trusty reports of this, since they're
probably the acroread crap. And point those bugs to here.
I editt
This doesn't happen on a normal Trusty system, but yeah, there are
similar reports of this happening to people. Must be some kind of
leftover stuff from upgrades. My system has an upgrade chain going back
to Edgy (6.10), but I keep it tidy with aptitude and other tools.
You may have some cruft i
** Summary changed:
- tab bash-completion adds an unwanted space so path name expansion fails
+ unwanted space after directory completion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372286
Title:
1 - 100 of 537 matches
Mail list logo
