unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: kfogel@red-bean.com, emacs-devel@gnu.org
Subject: Re: [PATCH] allow function values for `enable-local-eval'
Date: 30 Jun 2002 23:37:12 +0200	[thread overview]
Message-ID: <5x8z4wzbw7.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200206292222.g5TMMKx10256@santafe.santafe.edu>

Richard Stallman <rms@gnu.org> writes:

>       I'm working on a project where the files belonging to
>     one of the modules have a rather complicated -- but harmless -- eval:
> 
> Could you show it to us, please?
> 

I edited out the details but here it is:

 eval: (c-add-style "StyleX" (quote ((c-basic-offset . 4) (c-offsets-alist (label . *) ...))) t)

Even if we provided a c-add-style: hook similar to c-file-style:
I couldn't just replace the eval: with it...

First, I'm not in control of those files, so I'm not in a position to
change those files, so I have to live with that `eval:'.

Secondly, even if I could change the eval:, that would disturbe other
developers which are still using older versions of emacs (some are
still using 20.7, and are not going to change any time soon).

Consequently, for me, it would be really nice if I could check for
this specific hook and just say it's ok.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2002-06-30 21:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E17NLww-0005Cn-00@floss>
2002-06-28 17:41 ` [PATCH] allow function values for `enable-local-eval' Richard Stallman
     [not found]   ` <87u1nnnqlp.fsf@floss.i-did-not-set--mail-host-address--so-shoot-me>
2002-06-29  0:55     ` Kim F. Storm
2002-06-29 22:22       ` Richard Stallman
2002-06-30 21:37         ` Kim F. Storm [this message]
2002-07-01 14:10           ` Richard Stallman
2002-07-01 21:26             ` Kim F. Storm
2002-07-02 19:46               ` Richard Stallman
2002-07-02 20:11                 ` Stefan Monnier
2002-07-02 21:49                   ` Kim F. Storm
2002-07-04  7:07                   ` Richard Stallman
2002-07-04 15:28                     ` Stefan Monnier
2002-07-04 19:38                       ` Kim F. Storm
2002-07-04 18:46                         ` Stefan Monnier
2002-07-04 21:58                           ` Kim F. Storm
2002-07-05  1:26                           ` Miles Bader
2002-07-05 13:39                             ` Kai Großjohann
2002-07-04 19:36                     ` Kim F. Storm
2002-07-05 22:05                       ` Richard Stallman
2002-07-02 21:20                 ` Kim F. Storm
2002-07-04  7:06                   ` Richard Stallman
2002-07-04 15:13                     ` Stefan Monnier
2002-07-05 10:48                       ` Richard Stallman
2002-07-03  1:28             ` Kevin Ryde
2002-06-29 22:22     ` Richard Stallman
     [not found]       ` <877kkhlmgw.fsf@floss.i-did-not-set--mail-host-address--so-shoot-me>
2002-07-01 14:10         ` Richard Stallman

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=5x8z4wzbw7.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.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).