GNU bug report logs - #1948
confusion and bug in dabbrev.el

Previous Next

Package: emacs;

Reported by: Peter Tury <tury.peter <at> gmail.com>

Date: Sun, 18 Jan 2009 19:45:04 UTC

Severity: normal

Tags: confirmed, fixed, patch

Fixed in version 25.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 1948-quiet <at> debbugs.gnu.org (full text, mbox):

From: Stephen Berman <Stephen.Berman <at> gmx.net>
To: 1948-quiet <at> debbugs.gnu.org
Subject: dabbrev-eliminate-newlines
Date: Fri, 09 May 2008 14:01:53 +0200
[ resent from
  http://lists.gnu.org/archive/html/emacs-devel/2008-05/msg00619.html ]

If you have a buffer with this text: 
------8<------
First.  Second.
------>8------
and later in the buffer type `M-/ SPC M-/', Emacs (started with -Q)
inserts this:
------8<------
First. Second
------>8------

It was only by stepping through Dabbrev expansion with Edebug that I
learned that this behavior is due to dabbrev-eliminate-newlines, in
particular that it is t by default.  Before that I wasn't even aware of
this variable.  I think at the very least dabbrev-eliminate-newlines
should be documented in (emacs)Dabbrev Customization, and its doc string
should reflect the above behavior (currently it reads "*Non-nil means
dabbrev should not insert newlines.  Instead it converts them to
spaces.").  It might also be a good idea to go a step further and
separate the handling of newlines and spaces, letting them be
independently customizable.

Steve Berman




This bug report was last modified 9 years and 143 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.