From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: How to apply a minor mode to all buffers
Date: Sat, 20 Jan 2007 18:24:59 +0200 [thread overview]
Message-ID: <u7ivhvf6s.fsf@gnu.org> (raw)
In-Reply-To: <af9b506a0701190830l7e26cd08i37b2d8cf86678e2b@mail.gmail.com> (aguilar.james@gmail.com)
> Date: Fri, 19 Jan 2007 08:30:31 -0800
> From: "James Aguilar" <aguilar.james@gmail.com>
> Cc: help-gnu-emacs@gnu.org
>
> On 1/19/07, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > Actually, I'm not surprised at all that this functionality is missing . .
> > .
>
> Hmm, I figured that there might be a rationale. However, if that is true,
> then why are there global minor modes like global-font-lock-mode?
There are exceptions to every rule.
> This applies to several programming languages, text files, configuration
> files, and even non-files (I have a personal aversion to >80 chars in all
> files I edit). Since my only use for emacs is to edit these kinds of files,
> I'd like to have a guard at the end so that I can know when I'm over the
> line.
Then mode hooks are probably the way to go. I doubt that you use too
many major modes, so this boils down to crafting a dozen or so mode
hooks in your .emacs file. For the few exceptions, you can always
turn on the mode by hand.
You said you thought using mode hooks looks like a hack, but in fact
that is the normal Emacs way of accomplishing such goals.
next prev parent reply other threads:[~2007-01-20 16:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3212.1169056299.2155.help-gnu-emacs@gnu.org>
2007-01-18 3:20 ` How to apply a minor mode to all buffers Stefan Monnier
2007-01-18 21:08 ` Malte Spiess
2007-01-18 22:03 ` Drew Adams
2007-01-18 22:33 ` James Aguilar
2007-01-18 22:40 ` Drew Adams
2007-01-19 10:37 ` Eli Zaretskii
2007-01-19 16:30 ` James Aguilar
2007-01-19 17:06 ` Juanma Barranquero
2007-01-20 16:24 ` Eli Zaretskii [this message]
[not found] ` <mailman.3350.1169310294.2155.help-gnu-emacs@gnu.org>
2007-01-20 17:38 ` Robert Thorpe
2007-01-20 18:41 ` Lennart Borgman (gmail)
2007-01-22 6:55 ` Mathias Dahl
[not found] ` <mailman.3356.1169318483.2155.help-gnu-emacs@gnu.org>
2007-01-22 11:48 ` Robert Thorpe
2007-01-22 21:23 ` Eli Zaretskii
[not found] ` <mailman.3429.1169501014.2155.help-gnu-emacs@gnu.org>
2007-01-23 17:48 ` Robert Thorpe
2007-01-23 21:56 ` Eli Zaretskii
2007-01-22 16:59 ` Stefan Monnier
[not found] ` <mailman.3316.1169224240.2155.help-gnu-emacs@gnu.org>
2007-01-22 16:57 ` Stefan Monnier
2007-02-02 19:27 ` leoboiko
2007-02-03 15:29 ` Juanma Barranquero
2007-02-05 17:07 ` Leonardo Boiko
2007-02-05 22:14 ` Juanma Barranquero
2007-02-07 7:42 ` Kevin Rodgers
2007-02-08 12:10 ` Leonardo Boiko
[not found] ` <mailman.3919.1170444615.2155.help-gnu-emacs@gnu.org>
2007-02-07 17:22 ` Stefan Monnier
2007-02-07 17:51 ` Robert Thorpe
2007-02-08 12:23 ` Leonardo Boiko
2007-02-08 12:20 ` Leonardo Boiko
2007-02-08 12:30 ` Juanma Barranquero
[not found] ` <mailman.4176.1170937835.2155.help-gnu-emacs@gnu.org>
2007-02-08 16:26 ` Robert Thorpe
2007-02-08 22:39 ` Juanma Barranquero
[not found] ` <mailman.4209.1170974375.2155.help-gnu-emacs@gnu.org>
2007-02-09 11:48 ` Robert Thorpe
2007-02-09 12:46 ` Juanma Barranquero
2007-01-17 17:51 James Aguilar
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=u7ivhvf6s.fsf@gnu.org \
--to=eliz@gnu.org \
/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.
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).