emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#7292: closed (Inappropriate uses of toggle-read-on


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#7292: closed (Inappropriate uses of toggle-read-only?)
Date: Thu, 10 Nov 2011 02:20:02 +0000

Your message dated Wed, 09 Nov 2011 21:19:48 -0500
with message-id <address@hidden>
and subject line Re: bug#7292: view-mode clobbers speedbar bindings
has caused the debbugs.gnu.org bug report #7292,
regarding Inappropriate uses of toggle-read-only?
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
7292: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7292
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: view-mode clobbers speedbar bindings Date: Wed, 27 Oct 2010 20:03:10 -0400 User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.11) Gecko/20101025 Lightning/1.0b3pre Thunderbird/3.1.5
Hi,

A number of speedbar's bindings, such as 'n' and 'p', do not work with
view-mode enabled in the speedbar buffer (which makes no sense anyway). 
This is relevant when view-read-only is set, causing speedbar-mode to
implicitly enable view-mode.

For my part, I have redefined speedbar-mode in my .emacs file as follows:

(require 'speedbar)
(defvar real-speedbar-mode #'speedbar-mode)
(defun speedbar-mode ()
  (let ((view-read-only nil))
    (funcall #'real-speedbar-mode)))


This appears to solve the problem.  speedbar-mode calls
toggle-read-only; binding view-read-only to nil around that call should
be a more permanent fix.

M-x emacs-version
GNU Emacs 23.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of
2010-09-26 on falconsrevenge

Thanks,
Ryan Twitchell




--- End Message ---
--- Begin Message --- Subject: Re: bug#7292: view-mode clobbers speedbar bindings Date: Wed, 09 Nov 2011 21:19:48 -0500 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Version: 24.0.92

Stefan Monnier wrote:

> So let's add it to byte-compile-interactive-only-functions (with
> a comment about why); and if it turns out that there are many cases
> where calling it from Elisp makes sense, then we'll get to learn which
> are the cases where it makes sense.

Done.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]