[Aptitude-devel] Processed: Re: Bug#459984: aptitude: adding bash completion
Processing control commands: > close -1 Bug #459984 [aptitude] aptitude: adding bash completion Marked Bug as done -- 459984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#459984: aptitude: adding bash completion
Control: close -1 Hi, 2008-01-10 15:57 Daniel Burrows: On Thu, Jan 10, 2008 at 12:39:41AM +0100, Mathieu GELIwas heard to say: Package: aptitude Version: 0.4.10-1+b2 Severity: normal Tags: patch Completion seems to be required for some time. Here is a quick patch that should make bash users happy for main options. I'm not opposed to the concept, but if I type "aptitude ins", bash already expands "install". In fact, it even knows that subsequent arguments should be expanded as package names. This is apparently provided by /etc/bash_completion, and it appears to handle a more comprehensive set of options. Moreover, in the bash package it should be maintained by people who, unlike me, actually understand bash completion, so that seems like a more appropriate place for it to live. :-) Similar to Daniel Burrows, I would not have been opposed to add this file originally, but if this file is provided by "bash-completion" and has been for many years, I don't think that there's much sense to put it in aptitude 8 years later. (Besides that, there would be operational problems with aptitude trying to take over files from other packages). 2011-12-09 05:03 Daniel Hartwig: severity 459984 wishlist thanks Last point : aptitude completion data should I'm my opinion better sit in /etc/bash_completiion.d/ as a single file instead of being stacked in /etc/bash_completiion. This has been the case for some time: io:~$ dpkg -L bash-completion | grep aptitude /etc/bash_completion.d/aptitude Different location, but same thing: /usr/share/bash-completion/completions/aptitude Anyway here is new version based on the current version in testing which replaces dist-upgrade and upgrade with safe-upgrade and full-upgrade. I also added etc/bash_completion.d to aptitude.dirs and added ... The version in bash-completion has supported safe-/full-upgrade for some time. I am quite sure that it's still up-to-date, we didn't change many command line options and try to not break existing usage. So closing the report now. Cheers. -- Manuel A. Fernandez Montecelo ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
Re: [Aptitude-devel] Bug#435829: aptitude-[create|run]-state-bundle commands very annoying
Hi, Manuel A. Fernandez Montecelo wrote: > >Given aptitude-create-state-bundle/aptitude-run-state-bundle appear to > >be only for debug purposes, could they be moved to /usr/lib/aptitude or > >/usr/share/aptitude so that when someone wants to do a debug state save, > >they just have to type the whole path to the script. Many other > >packages put rarely needed scripts in such a place to avoid poluting the > >normal PATH environment. > > After almost a decade, things got worse over the years after this report > (with the binary named aptitude-curses and the now-disabled > aptitude-gtk, etc). I think that it's too late to address this now. JFTR: apti works for many years without issues: → aptitude completing external command aptitude completing alias aptitude-also-via-dependency aptitude-just-recommended aptitude-review-unmarkauto-libraries aptitude-upgradable-to-experimental aptitude-dpigsaptitude-newer-than-in-archive aptitude-upgradable-to-buildd Not sure what zsh makes differently, but it successfully hid that problem from me for as long as I can think back. (And I'm the one of the two current Aptitude maintainers who occassionally uses the aptitude-*-state-bundle commands.) Only if I type aptitude-c, these commands show up: → aptitude-c completing external command aptitude-create-state-bundle aptitude-curses > The solution is simple anyway, just adding the extra space, or creating > aliases if the same mistakes happen too often, etc. Or switching to zsh. ;-) SCNR, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Processed: Re: aptitude-[create|run]-state-bundle commands very annoying
Processing control commands: > tags -1 + wontfix Bug #435829 [aptitude] aptitude-[create|run]-state-bundle commands very annoying Added tag(s) wontfix. > close -1 Bug #435829 [aptitude] aptitude-[create|run]-state-bundle commands very annoying Marked Bug as done -- 435829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#435829: aptitude-[create|run]-state-bundle commands very annoying
Control: tags -1 + wontfix Control: close -1 Hi Lennart, 2007-08-03 14:45 Lennart Sorensen: Subject: aptitude-[create|run]-state-bundle commands very annoying Package: aptitude Version: 0.4.6.1-1 Severity: wishlist The new commands added to aptitude aptitude-create-state-bundle and aptitude-run-state-bundle are really annoying. After these were added tab completion has become much more annoying. Fro years I have been able to type apticommand and get aptitude command. Now I get aptitudecommand unless I remember to hit a space after tab. Given aptitude-create-state-bundle/aptitude-run-state-bundle appear to be only for debug purposes, could they be moved to /usr/lib/aptitude or /usr/share/aptitude so that when someone wants to do a debug state save, they just have to type the whole path to the script. Many other packages put rarely needed scripts in such a place to avoid poluting the normal PATH environment. After almost a decade, things got worse over the years after this report (with the binary named aptitude-curses and the now-disabled aptitude-gtk, etc). I think that it's too late to address this now. The solution is simple anyway, just adding the extra space, or creating aliases if the same mistakes happen too often, etc. It's a common problem with command-line interfaces that this issues arise when programs / options / files change between systems, appear in newer versions, etc. Even if we prevent this today, maybe tomorrow somebody comes up with aptitude-on-steroids and "breaks" things again. So closing the bug now. Cheers. -- Manuel A. Fernandez Montecelo___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#826624: Bug#826624: aptitude can't be stopped with "Q" but only with ^T and going down there
On Tue, Jun 07, 2016 at 02:19:40PM +0200, Axel Beckert wrote: > Hi Albrecht, > Albrecht Herzog wrote: > > On Tue, Jun 07, 2016 at 11:49:53AM +0200, Axel Beckert wrote: > > > Hi Albert, > Sorry for misspelling of your name in my previous mail. Try to forget it ASAP :-D)) Or did you mix it with Einstein? ROTFL :) > > > Did you press "q" or "Q" at least once before and cancelled it by > > > pressing either Ctrl-G or Escape? > > When presseing "q" to quit, there are still two lines staying there > What kind of lines? Well just two lines of te menue, white lessers on blue ground. > > Oh! > > OOHHH! > Not these two lines, right? :-) Sorry, just the two lines and nothing else. > > Q works. q doesn't > That sounds like a bug. So I'd be curious about where Q works, but q doesn't. :-) > > > And do you have dialogs in mini-buffers enabled? > > No. > Ok, so I've disabled mini-buffers temporarily in my setup, but found > no occassion related to quitting aptitude where Q works, but q doesn't. Curious, isn't it? > > bugreport can be closed ! > I'm not yet convinced. You may have found something there. :-) But I'm not proud of it. Regards, Albrecht ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#826624: Bug#826624: aptitude can't be stopped with "Q" but only with ^T and going down there
Hi Albrecht, Albrecht Herzog wrote: > On Tue, Jun 07, 2016 at 11:49:53AM +0200, Axel Beckert wrote: > > Hi Albert, Sorry for misspelling of your name in my previous mail. > > > I've got it when using "Q" > > Of course I did > > > Did you press "q" or "Q" at least once before and cancelled it by > > pressing either Ctrl-G or Escape? > > When presseing "q" to quit, there are still two lines staying there What kind of lines? > Oh! > OOHHH! Not these two lines, right? :-) > Q works. q doesn't That sounds like a bug. So I'd be curious about where Q works, but q doesn't. > > And do you have dialogs in mini-buffers enabled? > > No. Ok, so I've disabled mini-buffers temporarily in my setup, but found no occassion related to quitting aptitude where Q works, but q doesn't. > bugreport can be closed ! I'm not yet convinced. You may have found something there. :-) Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Processed: Re: Bug#826624: aptitude can't be stopped with "Q" but only with ^T and going down there
Processing control commands: > tag -1 + moreinfo unreproducible Bug #826624 [aptitude] aptitude can't be stopped with "Q" but only with ^T and going down there Added tag(s) moreinfo and unreproducible. -- 826624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#826624: Bug#826624: aptitude can't be stopped with "Q" but only with ^T and going down there
Control: tag -1 + moreinfo unreproducible Hi Albert, thanks for the bug report. Albrecht Herzog wrote: > Version: 0.6.11-1+b1 [...] >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I've got it when using "Q" Did you press "q" or "Q" at least once before and cancelled it by pressing either Ctrl-G or Escape? And do you have dialogs in mini-buffers enabled? >* What was the outcome of this action? > > Nothing at all This smells a lot like https://bugs.debian.org/607118 which got fixed after Jessie in 0.7.2-1. With one exception (and hence the "unreproducible" tag): If I can't quit Aptitude's TUI with "q" anymore in Jessie, quitting via the menu doesn't work anymore for me either. So it might be a different issue, though. So a few more questions to maybe narrow down the issue: * Does it happen always or occassionally? Or did it happen only once so far? * Do you have a chance to reproduce it? If so, can you also try to reproduce it in a Debian Unstable or Debian Testing environment? (A chroot or VM should suffice.) Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#826624: aptitude can't be stopped with "Q" but only with ^T and going down there
Package: aptitude Version: 0.6.11-1+b1 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Nothing special * What exactly did you do (or not do) that was effective (or ineffective)? I've got it when using "Q" * What was the outcome of this action? Nothing at all * What outcome did you expect instead? Stopping aptitude decently. *** End of the template - remove these template lines *** -- Package-specific info: Terminal: linux $DISPLAY not set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.11 compiled at Nov 8 2014 13:34:39 Compiler: g++ 4.9.1 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.4.0 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20140913 cwidget version: 0.5.17 Apt version: 4.12.0 aptitude linkage: linux-vdso.so.1 (0x7ffd518ea000) libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x7fd86c152000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7fd86bf1c000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fd86bcf2000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7fd86baec000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7fd86b7d6000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7fd86b50d000) libboost_iostreams.so.1.55.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7fd86b2f5000) libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7fd86aee4000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd86acc7000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fd86a9bc000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd86a6bb000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fd86a4a5000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd86a0fa000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fd869ef7000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd869cf3000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fd869ad8000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7fd8698c8000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fd8696a5000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd86949d000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fd869298000) /lib64/ld-linux-x86-64.so.2 (0x7fd86cb15000) -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common 0.6.11-1 ii libapt-pkg4.121.0.9.8.3 ii libboost-iostreams1.55.0 1.55.0+dfsg-3 ii libc6 2.19-18+deb8u4 ii libcwidget3 0.5.17-2 ii libgcc1 1:4.9.2-10 ii libncursesw5 5.9+20140913-1+b1 ii libsigc++-2.0-0c2a2.4.0-1 ii libsqlite3-0 3.8.7.1-1+deb8u1 ii libstdc++64.9.2-10 ii libtinfo5 5.9+20140913-1+b1 ii libxapian22 1.2.19-1+deb8u1 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.6.11-1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: pn apt-xapian-index pn debtags ii tasksel 3.31+deb8u1 -- no debconf information ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel