all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Why aren't paragraph-s\(tart\|eparate\) buffer local by default?
Date: Sun, 19 Jun 2005 11:55:47 -0400	[thread overview]
Message-ID: <E1Dk29D-0003zB-V8@fencepost.gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1050618210511.179B-100000@acm.acm> (message from Alan Mackenzie on Sat, 18 Jun 2005 21:17:31 +0000 (GMT))

    Why aren't paragraph-s\(tart\|eparate\) buffer local?  There doesn't seem
    to be any call for having global values for them since so many major
    modes (amongst them C Mode, Lisp mode, Texinfo mode) give these variables
    mode specific values.

There is certainly a reason for these variables to have global defaults.
The paragraph commands can be used even in Fundamental mode.

We could consider making them automatically local whenever set;
that doesn't require eliminating the global defaults.  I am not
sure this is bad, but it isn't obvious to me it is desirable.

I think the right fix for the problem you encountered is to make
c-set-style check that the buffer has an appropriate mode before it
does anything else.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click


  reply	other threads:[~2005-06-19 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18 21:17 Why aren't paragraph-s\(tart\|eparate\) buffer local by default? Alan Mackenzie
2005-06-19 15:55 ` Richard Stallman [this message]
2005-06-20 12:28 ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Dk29D-0003zB-V8@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.