Bug#543687: reportbug: Changing editor interactively (to vi) got me a vi session, but didn't edit the report.
tags 543687 unreproducible thanks Hello Edward, thanks for your bug report On Wed, Aug 26, 2009 at 15:10, Edward Welbourne wrote: > Package: reportbug > Version: 4.6 > Severity: normal > > > I have > export EDITOR=emacsclient > set in my environment. > > Today I installed emacs23 and immediately hit a bug (can't use rmail), > so fired up reportbug. When it came time for me to edit the bug > e-mail, I just got error messages in reportbug's virtual console; > emacsclient wasn't answering :-( > > So I opted (I think the command letter was "c") to change editor > command; I used vi, which was duly started up, but on an empty buffer, > instead of on the familiar buffer I expected to see, with package > details in it. could you please try with reportbug v4.8 ? I just test it and it works fine: mo...@zion:~$ export EDITOR=emacsclient mo...@zion:~$ reportbug -O --debug checkgmail Unrecognized token: ldap *** Welcome to reportbug. Use ? for help at prompts. *** Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Sandro Tosi ' as your from address. Getting status for checkgmail... Verifying package integrity... Will send report to Debian (per lsb_release). Maintainer for checkgmail is 'Sandro Tosi '. Looking up dependencies of checkgmail... Please briefly describe your problem (max. 100 characters allowed; you can elaborate in a moment; an empty response will stop reportbug). This will be the bug email subject, so write a concise summary of what is wrong with the package, for example, "fails to send email" or "does not start with -q option specified" (enter Ctrl+c to exit). > dagf Enter any additional addresses this report should be sent to; press ENTER after each address. Press ENTER on a blank line to continue. > How would you rate the severity of this problem or report? 1 criticalmakes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. 2 grave makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. 3 serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive); may or may not affect the usability of the package. Note that non-severe policy violations may be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also designate other bugs as 'serious' and thus release- critical; however, end users should not do so.) 4 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. 5 does-not-build a bug that stops the package from being built from source. (This is a 'virtual severity'.) 6 normal a bug that does not undermine the usability of the whole package; for example, a problem with a particular option or menu item. 7 minor things like spelling mistakes and other minor cosmetic errors that do not affect the core functionality of the package. 8 wishlistsuggestions and requests for new features. Please select a severity level: [normal] Do any of the following apply to this report? 1 l10n This bug reports a localization/internationalization issue. 2 patch You are including a patch to fix this problem. 3 none Please select tags: (one at a time) [none] Spawning emacsclient... emacsclient: can't find socket; have you started the server? To start the server in Emacs, type "M-x server-start". emacsclient: No socket or alternate editor. Please use: --socket-name --server-file (or environment variable EMACS_SERVER_FILE) --alternate-editor (or environment variable ALTERNATE_EDITOR) Warning: possible error exit from emacsclient: 256 No changes were made in the editor. Report will be sent to Sandro Tosi Submit this report on checkgmail (e to edit) [y|n|a|c|E|i|l|m|p|q|d|t|?]? ? y - Submit the bug report via email. n - Don't submit the bug report; instead, save it in a temporary file (exits reportbug). a - Attach a file. c - Change editor and re-edit. E - (default) Re-edit the bug report. i - Include a text file. l - Pipe the message through the pager. m - Choose a mailer to edit the report. p - print message to stdout. q - Save it in a temporary file and quit. d - Detach an attachment file. t - Add tags. ? - Display this help. Submit this report on checkgmail (e to edit) [y|n|a|c|E|i|l|m|p|q|d|t|?]? c Choose editor: vim Spawning vim... Report will be sent to Sandro Tosi Submit this report on checkgmail (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]? y Sending message via /usr/sbin/sendmail... Bug report submitted
Bug#543687: reportbug: Changing editor interactively (to vi) got me a vi session, but didn't edit the report.
The explanation for emacsclient's mis-behaviour when reporting *this* bug turns out to be fairly easy: emacs23 has installed its emacsclient and told the alternatives system to use that by default, so I was using emacs23's emacsclient with emacs22. The misbehaviour when I told reportbug to use vi, however, remains ... Eddy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#543687: reportbug: Changing editor interactively (to vi) got me a vi session, but didn't edit the report.
Package: reportbug Version: 4.6 Severity: normal I have export EDITOR=emacsclient set in my environment. Today I installed emacs23 and immediately hit a bug (can't use rmail), so fired up reportbug. When it came time for me to edit the bug e-mail, I just got error messages in reportbug's virtual console; emacsclient wasn't answering :-( So I opted (I think the command letter was "c") to change editor command; I used vi, which was duly started up, but on an empty buffer, instead of on the familiar buffer I expected to see, with package details in it. I described the problem, saved the result and exited; reportbug said I hadn't edited the report, so I tried again; I saw the same file I'd been editing previously. I told reportbug to show me the message it was going to send - it displayed something whose last few lines (my console is inside screen and doesn't respond usefully to anything that I expect to cause scroll-back; nor did reportbug think to pipe the file through a pager) looked like the normal package description that I *expected* to be editing, but hadn't seen. So I duly submitted the bug, over-riding reportbug's desire to abort because I wasn't changing text. Sure enough, when I got the auto-responder mail, I found the familiar package description information with no sign of the text I'd edited. I've now exited emacs23 and started up emacs22, so that I can run reportbug on itself - and sure enough, it invoked emacsclient; but I found myself with a buffer called "-dir" in the working directory in which I ran reportbug; and that directory turns out to contain a file called "-c" containing what I edited using vi. A quick grep of the ouptut from ps revealed emacsclient +6 /tmp/reportbug-reportbug-20090826-847-7U03sn so I opened the file that named - only to discover emacs already had a buffer open on it, that I merely hadn't yet seen (another bug for me to report on emacs). So now I'm editing that - who knows, it might even work. This may be a bug in emacsclient; but the fact that vi had similar problems suggests there *is* a bug in reportbug, whether that's provoking the emacsclient problem or merely independent and confusing. ... h ! I have some other suspicious-looking buffers open: -file0 Fundamental /tmp/-file -position0 Fundamental /tmp/-position screen.rxvt 0 Fundamental /tmp/screen.rxvt % 40 Fundamental /dev/pts/4 % -tty 0 Fundamental /dev/pts/-tty % -current-frame 0 Fundamental /dev/pts/-current-frame Again, this is probably emacsclient's fault, but may be material to investigating the reportbug issue ... -- Package-specific info: ** Environment settings: EDITOR="emacsclient" VISUAL="emacsclient" NAME="Edward Welbourne" INTERFACE="text" ** /disk/home/eddy/.reportbugrc: reportbug_version "3.44" mode standard ui text -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages reportbug depends on: ii apt 0.7.22.2 Advanced front-end for dpkg ii python2.5.4-2An interactive high-level object-o ii python-reportbug 4.6Python modules for interacting wit reportbug recommends no packages. Versions of packages reportbug suggests: pn debconf-utils (no description available) ii debsums 2.0.46 verification of installed package ii dlocate 1.02 fast alternative to dpkg -L and dp ii exim4-daemon-light [mail-tran 4.69-11lightweight Exim MTA (v4) daemon ii file 5.03-1 Determines file type using "magic" ii gnupg 1.4.9-4GNU privacy guard - a free PGP rep pn python-gnome2-extras (no description available) ii python-gtk2 2.14.1-3 Python bindings for the GTK+ widge pn python-urwid (no description available) ii python-vte1:0.20.5-1 Python bindings for the VTE widget ii xdg-utils 1.0.2-6.1 desktop integration utilities from -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
