2020-09-23 01:12:40 +08:00
|
|
|
function __fish_print_apt_packages
|
|
|
|
|
argparse --name=__fish_print_packages i/installed -- $argv
|
|
|
|
|
or return
|
|
|
|
|
|
|
|
|
|
switch (commandline -ct)
|
|
|
|
|
case '-**'
|
|
|
|
|
return
|
|
|
|
|
end
|
|
|
|
|
|
Stringify apt completions again
Commit 09685c36826c5d5d41565e00ed2d92e67997ac6a tried making the apt
completions faster by doing two things:
1. Introduce a limiting "head"
2. Re-replace our "string" usage with tr
Unfortunately, in doing so it introduced a few issues:
1. The "tr" had a dangling "+" so it cut apart package
descriptions that contained a "+".
This caused e.g. "a C++ library" to generate another completion
candidate, "library".
2. In reusing "tr" it probably reintroduced #8575,
as tr is not 8-bit-clean.
3. It filtered too early, on the raw apt-cache output,
which caused it to fill up with long descriptions.
So e.g. for "texlive" it would only generate 10 completions,
where it should have matched 54 packages.
Because most of the speedup is in the "head" stopping early, we
instead go back to the old string way, but introduce a limiting "head"
after the "sed" (which will have removed everything but the package
name line and the first line of the description)
In my tests this is about ~10% slower than doing head early and using
tr, but it's more correct.
Admittedly I haven't been able to reproduce the 35s scenario that
09685 talks about, but the most likely cause of that is *apt-cache*
being slow - I don't see how string can be that much slower on another
system - and so it will most likely also be fixed by doing head here.
Future possibilities here include:
1. Using "apt-cache search --names-only", which gives a much nicer
format (but only for non-installed packages - the search strings are
apparently ANDed?)
2. Switching to `string split`, possibly using NUL and using `string
split0`?
3. Introducing a `string --null-in` switch so we can get by with one
`string`
4. (multi-threaded execution so the `string`s run in parallel)
2022-09-23 21:30:42 +08:00
|
|
|
type -q -f apt-cache || return 1
|
2020-09-23 01:24:04 +08:00
|
|
|
if not set -q _flag_installed
|
Stringify apt completions again
Commit 09685c36826c5d5d41565e00ed2d92e67997ac6a tried making the apt
completions faster by doing two things:
1. Introduce a limiting "head"
2. Re-replace our "string" usage with tr
Unfortunately, in doing so it introduced a few issues:
1. The "tr" had a dangling "+" so it cut apart package
descriptions that contained a "+".
This caused e.g. "a C++ library" to generate another completion
candidate, "library".
2. In reusing "tr" it probably reintroduced #8575,
as tr is not 8-bit-clean.
3. It filtered too early, on the raw apt-cache output,
which caused it to fill up with long descriptions.
So e.g. for "texlive" it would only generate 10 completions,
where it should have matched 54 packages.
Because most of the speedup is in the "head" stopping early, we
instead go back to the old string way, but introduce a limiting "head"
after the "sed" (which will have removed everything but the package
name line and the first line of the description)
In my tests this is about ~10% slower than doing head early and using
tr, but it's more correct.
Admittedly I haven't been able to reproduce the 35s scenario that
09685 talks about, but the most likely cause of that is *apt-cache*
being slow - I don't see how string can be that much slower on another
system - and so it will most likely also be fixed by doing head here.
Future possibilities here include:
1. Using "apt-cache search --names-only", which gives a much nicer
format (but only for non-installed packages - the search strings are
apparently ANDed?)
2. Switching to `string split`, possibly using NUL and using `string
split0`?
3. Introducing a `string --null-in` switch so we can get by with one
`string`
4. (multi-threaded execution so the `string`s run in parallel)
2022-09-23 21:30:42 +08:00
|
|
|
# Do not generate the cache as apparently sometimes this is slow.
|
|
|
|
|
# http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547550
|
|
|
|
|
# (It is safe to use `sed -r` here as we are guaranteed to be on a GNU platform
|
|
|
|
|
# if apt-cache was found.)
|
|
|
|
|
# Uses the UTF-8/ASCII record separator (0x1A) character.
|
|
|
|
|
#
|
|
|
|
|
# Note: This can include "Description:" fields which we need to include,
|
|
|
|
|
# "Description-en_GB" (or another locale code) fields which we need to include
|
|
|
|
|
# as well as "Description-md5" fields which we absolutely do *not* want to include
|
2022-10-04 07:29:41 +08:00
|
|
|
# The regex doesn't allow numbers, so unless someone makes a hash algorithm without a number
|
|
|
|
|
# in the name, we're safe. (yes, this should absolutely have a better format).
|
Stringify apt completions again
Commit 09685c36826c5d5d41565e00ed2d92e67997ac6a tried making the apt
completions faster by doing two things:
1. Introduce a limiting "head"
2. Re-replace our "string" usage with tr
Unfortunately, in doing so it introduced a few issues:
1. The "tr" had a dangling "+" so it cut apart package
descriptions that contained a "+".
This caused e.g. "a C++ library" to generate another completion
candidate, "library".
2. In reusing "tr" it probably reintroduced #8575,
as tr is not 8-bit-clean.
3. It filtered too early, on the raw apt-cache output,
which caused it to fill up with long descriptions.
So e.g. for "texlive" it would only generate 10 completions,
where it should have matched 54 packages.
Because most of the speedup is in the "head" stopping early, we
instead go back to the old string way, but introduce a limiting "head"
after the "sed" (which will have removed everything but the package
name line and the first line of the description)
In my tests this is about ~10% slower than doing head early and using
tr, but it's more correct.
Admittedly I haven't been able to reproduce the 35s scenario that
09685 talks about, but the most likely cause of that is *apt-cache*
being slow - I don't see how string can be that much slower on another
system - and so it will most likely also be fixed by doing head here.
Future possibilities here include:
1. Using "apt-cache search --names-only", which gives a much nicer
format (but only for non-installed packages - the search strings are
apparently ANDed?)
2. Switching to `string split`, possibly using NUL and using `string
split0`?
3. Introducing a `string --null-in` switch so we can get by with one
`string`
4. (multi-threaded execution so the `string`s run in parallel)
2022-09-23 21:30:42 +08:00
|
|
|
#
|
|
|
|
|
# aptitude has options that control the output formatting, but is orders of magnitude slower
|
|
|
|
|
#
|
|
|
|
|
# sed could probably do all of the heavy lifting here, but would be even less readable
|
|
|
|
|
#
|
2022-10-04 07:29:41 +08:00
|
|
|
# The `head -n 500` causes us to stop once we have 500 lines. We do it after the `sed` because
|
|
|
|
|
# Debian package descriptions can be extremely long and are hard-wrapped: texlive-latex-extra
|
|
|
|
|
# has about 2700 lines on Debian 11.
|
|
|
|
|
apt-cache --no-generate show '.*'(commandline -ct)'.*' 2>/dev/null | sed -r '/^(Package|Description-?[a-zA-Z_]*):/!d;s/Package: (.*)/\1\t/g;s/Description-?[^:]*: (.*)/\1\x1a\n/g' | head -n 500 | string join "" | string replace --all --regex \x1a+ \n | uniq
|
2020-09-23 01:12:40 +08:00
|
|
|
return 0
|
|
|
|
|
else
|
|
|
|
|
set -l packages (dpkg --get-selections | string replace -fr '(\S+)\s+install' "\$1" | string match -e (commandline -ct))
|
2022-10-04 07:29:41 +08:00
|
|
|
apt-cache --no-generate show $packages 2>/dev/null | sed -r '/^(Package|Description-?[a-zA-Z_]*):/!d;s/Package: (.*)/\1\t/g;s/Description-?[^:]*: (.*)/\1\x1a\n/g' | head -n 500 | string join "" | string replace --all --regex \x1a+ \n | uniq
|
2020-09-23 01:12:40 +08:00
|
|
|
return 0
|
|
|
|
|
end
|
|
|
|
|
end
|