unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: "Andreas Röhler" <andreas.roehler@online.de>, emacs-devel@gnu.org
Subject: Re: beginning-of-defun (again)
Date: Thu, 29 Oct 2015 13:03:34 +0100	[thread overview]
Message-ID: <87lhal990p.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87twp951ug.fsf@gmail.com> (Oleh Krehel's message of "Thu, 29 Oct 2015 12:52:07 +0100")

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?

> The only relevant setting is 0 or non-zero (the default).

Huh?!?  The only relevant settings are nil and non-nil.

> Setting it to 0 seems to do nothing. Maybe someone could explain what
> it actually does.

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

   "This is a string and it continues
(on the next line..."

or

(list
(missing-indentation

or something like that.

>> 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.

> And there's nothing else that makes "(" be on a new line, except for
> rare cases in docstrings, where it can be escaped.

In Elisp perhaps, but that variable is equally valid in Scheme.  And
rewrapping a comment string might move a ( to the start of a line
without auto-escaping it in the process.  Though the frequency of this
happening to me when editing Scheme files has decreased to a degree
where I suspect Emacs to be actively avoiding it these days.

> So it seems that the problem is already solved in a good way, without
> having to customize anything.

-- 
David Kastrup



  reply	other threads:[~2015-10-29 12:03 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 [this message]
2015-10-29 13:07     ` Oleh Krehel
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=87lhal990p.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.org \
    --cc=ohwoeowho@gmail.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).