From: Nikolaus Rath <Nikolaus@rath.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The current state of the comment-cache branch
Date: Thu, 29 Dec 2016 08:56:25 -0800 [thread overview]
Message-ID: <87wpei7jye.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <83d1gbv1rt.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Dec 2016 05:43:02 +0200")
On Dec 29 2016, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Nikolaus Rath <Nikolaus@rath.org>
>> Cc: emacs-devel@gnu.org
>> Date: Wed, 28 Dec 2016 15:58:53 -0800
>>
>> >> I would hope that Emacs is used not only to edit its own source code but
>> >> also other code, for which these standards don't apply.
>> >
>> > It is, but how is that relevant to the issue at hand? The issue at
>> > hand is how does open-paren-in-column-0-is-defun-start affect C code
>> > editing. The intent of my reference to GNU standards was to point
>> > out that having an opening brace in column zero is a very frequent
>> > situation in the C sources of any GNU project, and therefore saying
>> > this convention is not useful for C flies in the face of the reality
>> > right under our feet.
>>
>> What I meant is that setting open-paren-in-column-0-is-defun-start to t
>> in general is not a good idea, because it does not work for all C
>> files. So for this option to be useful, you'd have to do set it
>> conditionally - which IMO restricts its usefulness a lot.
>
> We have that option set to t for a long time, so the decision whether
> to do it was already made, and any problems that could cause are
> already with us.
Yes. Therefore, I think applying a patch that eliminates the need for it
completely would be a good thing.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2016-12-29 16:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 21:50 The current state of the comment-cache branch Alan Mackenzie
2016-12-24 1:32 ` Stefan Monnier
2016-12-24 9:07 ` Alan Mackenzie
2016-12-24 1:33 ` Stefan Monnier
2016-12-24 8:40 ` Alan Mackenzie
2016-12-24 20:56 ` Stephen Leake
2016-12-25 15:47 ` Stefan Monnier
2016-12-25 20:41 ` Richard Stallman
2016-12-24 8:02 ` Eli Zaretskii
2016-12-24 8:30 ` Alan Mackenzie
2016-12-24 8:55 ` Eli Zaretskii
2016-12-24 9:42 ` Alan Mackenzie
2016-12-24 11:11 ` Elias Mårtenson
2016-12-24 11:36 ` Alan Mackenzie
2016-12-24 12:00 ` Eli Zaretskii
2016-12-24 21:48 ` Andreas Röhler
[not found] ` <CADtN0W+7zHzuoWFrzs6MuonUM74D_dC+yh10rSk+r0nuxgeTBg@mail.gmail.com>
[not found] ` <CADtN0WJYXRg=oEBxn3UPjF6RFJG62nG4GpUFaphdkj9Egde_4Q@mail.gmail.com>
2016-12-24 12:21 ` Elias Mårtenson
2016-12-27 17:55 ` Alan Mackenzie
2016-12-28 15:36 ` Eli Zaretskii
2016-12-28 16:42 ` Alan Mackenzie
2016-12-28 16:45 ` Nikolaus Rath
2016-12-28 17:09 ` Eli Zaretskii
2016-12-28 23:58 ` Nikolaus Rath
2016-12-29 3:43 ` Eli Zaretskii
2016-12-29 16:56 ` Nikolaus Rath [this message]
2016-12-29 17:46 ` Eli Zaretskii
2016-12-29 19:44 ` Alan Mackenzie
2016-12-30 10:29 ` Andreas Röhler
2017-01-03 17:39 ` Stefan Monnier
2017-01-20 18:58 ` Andreas Röhler
2017-01-20 21:48 ` Stefan Monnier
2017-01-21 9:06 ` Andreas Röhler
2017-01-22 4:28 ` Stefan Monnier
2016-12-28 17:15 ` Stefan Monnier
2016-12-29 1:38 ` Richard Stallman
2016-12-29 2:15 ` Stefan Monnier
2016-12-24 12:27 ` Eli Zaretskii
2016-12-24 22:19 ` Paul Eggert
2016-12-25 16:07 ` Stefan Monnier
2016-12-25 16:30 ` Eli Zaretskii
2016-12-28 8:37 ` Alan Mackenzie
2016-12-28 17:02 ` Stefan Monnier
2016-12-28 17:10 ` Stefan Monnier
2016-12-27 16:40 ` Alan Mackenzie
2016-12-28 15:35 ` Eli Zaretskii
2016-12-28 16:35 ` Alan Mackenzie
2016-12-24 18:54 ` Richard Stallman
2016-12-27 16:11 ` Alan Mackenzie
2016-12-28 1:40 ` Dmitry Gutov
2016-12-28 7:54 ` Alan Mackenzie
2016-12-29 1:13 ` Dmitry Gutov
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=87wpei7jye.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--cc=eliz@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.