From: Raoul Gough <raoulgough@yahoo.co.uk>
Subject: viper-go-away is lame
Date: Thu, 11 Jan 2007 23:07:48 +0000 [thread overview]
Message-ID: <uk5ztxiuz.fsf@yahoo.co.uk> (raw)
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.
Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.
In GNU Emacs 21.3.1 (i386-msvc-nt5.0.2195)
of 2003-03-28 on buffy
configured using `configure --with-msvc (12.00)'
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: ENA
locale-coding-system: iso-latin-1
default-enable-multibyte-characters: t
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
The function viper-go-away doesn't do a very good job of "exiting"
viper, because the next time you open a file, it reverts Emacs back
into viper-mode.
e. g.
M-x viper
M-x viper-go-away
C-x C-f foo.txt ;; viper "restarts" itself here
This is caused by viper-go-away not cleaning up the changes viper made
to default-major-mode, initial-major-mode and find-file-hooks. The
following additions to viper-go-away should do the trick, maybe
there's a better way to fix the find-file-hooks via viper-remove-hooks
but I'm not sure.
(remove-hook 'find-file-hooks 'set-viper-state-in-major-mode)
(if (eq default-major-mode 'viper-mode)
(setq default-major-mode 'fundamental-mode))
(setq initial-major-mode 'lisp-interaction-mode)
By the way, viper.el in the CVS head *appears* to have the same
deficiency, but I haven't tested it.
--
Raoul Gough.
Send instant messages to your online friends http://uk.messenger.yahoo.com
reply other threads:[~2007-01-11 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uk5ztxiuz.fsf@yahoo.co.uk \
--to=raoulgough@yahoo.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).