GNU bug report logs - #20761
beginning-of-defun matches column 0 paren inside string literal

Previous Next

Package: emacs;

Reported by: Andreas Röhler <andreas.roehler <at> easy-emacs.de>

Date: Sun, 7 Jun 2015 17:22:02 UTC

Severity: wishlist

Tags: fixed

Merged with 20284, 26642

Found in versions 25.0.50, 25.0.50.1, 25.1, 25.2

Fixed in version 27.1

Done: Noam Postavsky <npostavs <at> users.sourceforge.net>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Nicolas Richard <youngfrog <at> members.fsf.org>
Cc: Glenn Morris <rgm <at> gnu.org>, 20761 <at> debbugs.gnu.org
Subject: bug#20761: 25.0.50.1, beginning-of-defun matches inside string
Date: Mon, 08 Jun 2015 07:45:40 +0200
Am 08.06.2015 um 07:18 schrieb Nicolas Richard:
> Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:
>> Am 07.06.2015 um 20:13 schrieb Glenn Morris:
>>> Andreas Röhler wrote:
>>>
>>>> (defun asdf ()
>>>>     "
>>>> (defun foo1 (&optional beg end)
>>>>     sdsd"
>>>> )
>>> Unescaped paren in column 0.
>> Can't a string have that?
> They can, but the convention is to not do that :
> (info "(emacs) Left Margin Paren")

An oddity from times, where parse-partial-sexp was not available, time 
to get rid of that.


> It's also in the docstring of beginning-of-defun
>> When `open-paren-in-column-0-is-defun-start' is non-nil, a defun
>> is assumed to start where there is a char with open-parenthesis
>> syntax at the beginning of a line.

Ditto, just legacy, no need for that.





This bug report was last modified 7 years and 104 days ago.

Previous Next


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