all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: bug-gnu-emacs@gnu.org
Subject: bug#2002: `beginning-of-defun' pushes mark undocumentedly. It shouldn't!
Date: Fri, 23 Jan 2009 11:27:14 +0000	[thread overview]
Message-ID: <20090123112714.GA3056@muc.de> (raw)

Hi, Emacs!

I was "horrified" to find `beginning-of-defun' pushes the mark.  OK,
maybe I should wake up, this having been done as long ago as 2004-05-01
in .../emacs-lisp/lisp.el 1.53.

However, this pushing of the mark is NOT DOCUMENTED, neither in the
Emacs nor the Elisp manual.  THIS IS A BUG!!!!

This marking is fine (maybe) when a user types C-M-a.  Actually, I think
it's of marginal utility - it's about as likely to be a nuisance as to
be helpful.

The marking is NOT ACCEPTABLE when begining-of-defun is used in a lisp
program.  Using b-o-d in a program is a reasonable thing to do.

The feature, if it is to remain must be documented in both manuals.  OK,
I'm volunteering to do this.  ;-)

POSSIBLE FIXES
==============

1. A new customizable option, with a name better than
`defun-movement-leaves-mark'.  This could be bound to nil by lisp
programs.

2. Document that lisp programs should use `beginning-of-defun-raw'.
(Does this exist in XEmacs?).

3. Revert b-o-d to leaving the mark well alone.

What do people think?

-- 
Alan Mackenzie (Nuremberg, Germany).







             reply	other threads:[~2009-01-23 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090125234411.GB6588@muc.de>
2009-01-23 11:27 ` Alan Mackenzie [this message]
2009-01-24  0:52   ` bug#2002: `beginning-of-defun' pushes mark undocumentedly. It shouldn't! Glenn Morris
2009-01-25 23:36     ` Alan Mackenzie
2009-01-25 23:35   ` bug#2002: marked as done (`beginning-of-defun' pushes mark undocumentedly. It shouldn't!) Emacs bug Tracking System

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=20090123112714.GA3056@muc.de \
    --to=acm@muc.de \
    --cc=2002@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@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.