all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "John Wiegley" <johnw@newartisans.com>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: andreas.roehler@online.de, Richard Stallman <rms@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: beginning-of-defun (again)
Date: Fri, 30 Oct 2015 11:17:26 -0700	[thread overview]
Message-ID: <m2a8r08bm1.fsf@Vulcan.attlocal.net> (raw)
In-Reply-To: <87twp8wvop.fsf@gmail.com> (Oleh Krehel's message of "Fri, 30 Oct 2015 10:29:58 +0100")

>>>>> Oleh Krehel <ohwoeowho@gmail.com> writes:

> If they are within macros, they're data and not defuns in my mind. For me, a
> defun is a top-level expression with "(" at column 0. It doesn't even need
> to define something callable (like `defun' or `defmacro'), so a `defcustom'
> statement is a defun for purposes of `beginning-of-defun'.

I realize you think this, Oleh; what I'm saying is that not everyone does.

As I mentioned, I'm fine with using column 0 as a heuristic. However, there
are use cases where it is confusing (I *still* hit C-M-x on nested defun's,
and find myself surprised that it does something else; and this despite
knowing the nature of the beast full well, and after many years of experience
of it not working).

Some people see "defun" and think this establishes a sort of syntactic entity
with regard to Emacs commands relating to defuns. What we're talking about is
a technical distinction that makes life easier for us -- and not about users
who find it confusing.

Since the decision is to go with the status quo, is there anything to discuss?

John



  reply	other threads:[~2015-10-30 18:17 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=m2a8r08bm1.fsf@Vulcan.attlocal.net \
    --to=johnw@newartisans.com \
    --cc=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.org \
    --cc=ohwoeowho@gmail.com \
    --cc=rms@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.