From: Oleh Krehel <ohwoeowho@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: "Andreas Röhler" <andreas.roehler@online.de>, emacs-devel@gnu.org
Subject: Re: beginning-of-defun (again)
Date: Thu, 29 Oct 2015 14:07:17 +0100 [thread overview]
Message-ID: <87oafhesca.fsf@gmail.com> (raw)
In-Reply-To: <87lhal990p.fsf@fencepost.gnu.org> (David Kastrup's message of "Thu, 29 Oct 2015 13:03:34 +0100")
David Kastrup <dak@gnu.org> writes:
> Oleh Krehel <ohwoeowho@gmail.com> writes:
>
>> Hi Andreas,
>>
>> Andreas Röhler <andreas.roehler@online.de> writes:
>>
>>> maybe it's time to have a reasonable default-behavior of
>>> beginning-of-defun in Emacs Lisp.
>>
>> I think it works pretty well as is.
>>
>>> open-paren-in-column-0-is-defun-start
>>
>> It's a strange variable that doesn't seem to do anything.
>
> Huh?
Please give an example then. I'm not able to see a difference when it's
unset.
>> The only relevant setting is 0 or non-zero (the default).
>
> Huh?!? The only relevant settings are nil and non-nil.
The only relevant use is:
if (!open_paren_in_column_0_is_defun_start)
{
find_start_value = BEGV;
find_start_value_byte = BEGV_BYTE;
goto found;
}
Note that it's not checked against Qnil. It may be that Qnil is
conveniently defined to be 0 though, I'm not sure.
> Speeds up syntax highlighting by giving it anchor points. If you
> encounter
>
> (
>
> in a file, that counts as the start of some list even without looking
> whether it might be part of something like
I see. I wonder what the speed-up factor is. For example in org.el.
>>> A function resp. top-level-form starts if the beginning of a list is
>>> followed by a respective keyword.
>>> The list of keywords being customizable seems a plus :)
>>
>> There's no reason for a defun to not start on a newline.
>
> But there's a reason for non-defuns to start on a newline.
I call these defuns anyway.
next prev parent reply other threads:[~2015-10-29 13:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 11:24 beginning-of-defun (again) Andreas Röhler
2015-10-29 11:52 ` Oleh Krehel
2015-10-29 12:03 ` David Kastrup
2015-10-29 13:07 ` Oleh Krehel [this message]
2015-10-29 13:28 ` David Kastrup
2015-10-29 13:47 ` David Kastrup
2015-10-29 17:39 ` Andreas Röhler
2015-10-29 12:11 ` Andreas Röhler
2015-10-29 12:16 ` Kaushal Modi
2015-10-29 17:56 ` John Wiegley
2015-10-30 1:35 ` Richard Stallman
2015-10-30 2:20 ` John Wiegley
2015-10-30 9:29 ` Oleh Krehel
2015-10-30 18:17 ` John Wiegley
2015-10-30 23:13 ` Richard Stallman
2015-10-30 23:29 ` Alan Mackenzie
2015-10-30 23:34 ` John Wiegley
2015-11-01 1:05 ` Richard Stallman
2015-10-29 12:46 ` Alan Mackenzie
2015-10-29 12:56 ` Andreas Röhler
2015-10-29 13:31 ` David Kastrup
2015-10-29 14:46 ` Andreas Röhler
2015-10-29 14:57 ` David Kastrup
2015-10-29 14:14 ` Alan Mackenzie
2015-10-30 1:34 ` Richard Stallman
2015-10-30 6:47 ` Andreas Röhler
2015-10-30 23:14 ` Richard Stallman
2015-10-31 8:01 ` Andreas Röhler
2015-10-31 12:24 ` David Kastrup
2015-10-31 15:55 ` Andreas Röhler
2015-11-01 1:06 ` 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=87oafhesca.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=andreas.roehler@online.de \
--cc=dak@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 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).