From: Dmitry Gutov <dgutov@yandex.ru>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 17247@debbugs.gnu.org
Subject: bug#17247: 24.4.50; end-of-defun bug in elisp
Date: Tue, 20 May 2014 15:12:18 +0300 [thread overview]
Message-ID: <537B46A2.1060705@yandex.ru> (raw)
In-Reply-To: <537B0B49.6000505@easy-emacs.de>
On 20.05.2014 10:59, Andreas Röhler wrote:
> AFAIU the purpose is to make sure the beginning of current defun is
> fetched, not the previous one, i.e. protect for cases, point is at the
> beginning of defun.
Guess so. So with the proposed change, the point at the beginning of a
defun doesn't "belong" to it anymore, but is considered "between defuns"
instead. Seems to work fine, at least with the given Elisp example and a
couple similar ones, with small differences.
> IMHO that end-of-defun section is over-engineered, thus bug-sourcing.
>
> For example the common design-logic when taking numeric arguments: with
> positiv go forward, with negativ backward, resp. negate assumed direction.
>
> This seems broken internally by (funcall end-of-defun-function), which
> doesn't care for arguments.
The additional logic seems to be there to differentiate between two
cases: we are inside a defun (beginning-of-defun followed by
end-of-defun will move point forward), we are between defuns
(beginning-of-defun followed by end-of-defun will move point backward),
and handle them appropriately.
next prev parent reply other threads:[~2014-05-20 12:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 6:04 bug#17247: 24.4.50; end-of-defun bug in elisp Leo Liu
2014-04-23 7:19 ` Andreas Röhler
2014-05-20 4:01 ` Dmitry Gutov
2014-05-20 7:59 ` Andreas Röhler
2014-05-20 12:12 ` Dmitry Gutov [this message]
2014-05-20 15:59 ` Andreas Röhler
2014-05-20 16:39 ` Dmitry Gutov
2014-05-20 14:18 ` Stefan Monnier
2014-05-20 16:33 ` Andreas Röhler
2014-05-20 14:20 ` Stefan Monnier
2014-05-20 16:32 ` Dmitry Gutov
2014-05-20 18:56 ` Stefan Monnier
2014-05-21 2:47 ` 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=537B46A2.1060705@yandex.ru \
--to=dgutov@yandex.ru \
--cc=17247@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
/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.