unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: mark.lillibridge@hp.com
Cc: 4887@emacsbugs.donarmstrong.com
Subject: bug#4887: 23.1; list-load-path-shadows produces broken buffer
Date: Wed, 11 Nov 2009 15:40:48 -0500	[thread overview]
Message-ID: <jwvljiclsam.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <200911111808.nABI8bCo021498@mailhub-pa1.hpl.hp.com> (Mark Lillibridge's message of "Wed, 11 Nov 2009 10:08:37 -0800")

>     Should linum use a different implementation method than
> define-globalized-minor-mode?  (does one exist?)

You mean global-linum-mode?  Yes, it could use a different method,
e.g. setting global hooks instead, but that might prove tricky.

>     Should we instead fix define-globalized-minor-mode to work with all
> buffers?  Its documentation via ^h f claims it works in every buffer:

That would be the best solution, yes.

Given the hooks we currently have, it's not very easy because buffers
like *Shadows* get created without running any hook, so basically the
first hook that would get triggered might be something like
window-configuration-change-hook, but that hooks has no easy way to
decide whether that buffer was just created recently or on the contrary
has been around for a long while (in which case enabling linum-mode
might be very wrong since the user may have turned it off there
earlier).

An easier solution is to not change anything to
define-globalized-minor-mode and to require Elisp code to explicitly set
a major mode for any buffer that will be displayed.  E.g. for *Shadows*
the Elisp code should explicitly call fundamental-mode in it.


        Stefan





  reply	other threads:[~2009-11-11 20:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08  5:34 bug#4887: 23.1; list-load-path-shadows produces broken buffer Mark Lillibridge
2009-11-09 19:14 ` Glenn Morris
2009-11-11 18:08   ` Mark Lillibridge
2009-11-11 20:40     ` Stefan Monnier [this message]
2009-11-13 21:57       ` Mark Lillibridge
2010-01-07  5:35         ` Mark Lillibridge
2010-01-07  5:48           ` Glenn Morris
2010-01-10  0:47             ` Mark Lillibridge
2010-01-11  1:52               ` Glenn Morris

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=jwvljiclsam.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=4887@emacsbugs.donarmstrong.com \
    --cc=mark.lillibridge@hp.com \
    /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).