From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Alan Mackenzie <acm@muc.de>
Cc: 24870@debbugs.gnu.org, Matt Armstrong <marmstrong@google.com>,
npostavs@users.sourceforge.net
Subject: bug#24870: 26.0.50; parse-partial-sexp ignores comment-end
Date: Thu, 15 Dec 2016 18:59:39 +0100 [thread overview]
Message-ID: <bf39d6fc-a8fa-308b-ff31-ff53484937eb@easy-emacs.de> (raw)
In-Reply-To: <20161215165011.GB2437@acm.fritz.box>
On 15.12.2016 17:50, Alan Mackenzie wrote:
> You commented lately on the effect of narrowing and how simply to
>> respect its results. Nothing further to say here.
> I don't see what your meaning is here, but never mind.
Referred to your post at emacs-devel 11.12.2016 11:17:
At the moment, narrowing is a strong, direct, simple facility - it does
what it says it does and no more.
next prev parent reply other threads:[~2016-12-15 17:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 19:38 bug#24870: 26.0.50; parse-partial-sexp ignores comment-end Andreas Röhler
2016-11-30 9:10 ` Matt Armstrong
2016-11-30 12:37 ` Andreas Röhler
2016-11-30 23:02 ` Matt Armstrong
2016-12-01 1:17 ` npostavs
2016-12-01 8:24 ` Andreas Röhler
2016-12-14 3:00 ` npostavs
2016-12-14 4:04 ` npostavs
2016-12-14 6:45 ` Andreas Röhler
2016-12-14 19:56 ` Alan Mackenzie
2016-12-15 8:18 ` Andreas Röhler
2016-12-15 16:01 ` Eli Zaretskii
2016-12-15 16:50 ` Alan Mackenzie
2016-12-15 17:59 ` Andreas Röhler [this message]
2016-12-14 21:58 ` Alan Mackenzie
2016-12-15 16:33 ` Noam Postavsky
2016-12-15 16:44 ` Alan Mackenzie
2016-12-18 5:39 ` npostavs
2016-12-29 11:14 ` Alan Mackenzie
2016-12-30 1:55 ` npostavs
2017-01-13 2:07 ` npostavs
2017-01-23 20:12 ` Alan Mackenzie
2017-01-24 0:30 ` npostavs
2016-12-01 8:33 ` Andreas Röhler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf39d6fc-a8fa-308b-ff31-ff53484937eb@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=24870@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=marmstrong@google.com \
--cc=npostavs@users.sourceforge.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).