From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: nbtrap@nbtrap.com, 16413@debbugs.gnu.org
Subject: bug#16413: 24.3.50; Inconsistent behavior of text property functions in narrowed buffer
Date: Sat, 11 Jan 2014 10:12:57 +0200 [thread overview]
Message-ID: <834n5baqd2.fsf@gnu.org> (raw)
In-Reply-To: <52D0FADE.8060605@dancol.org>
> Date: Sat, 11 Jan 2014 00:03:42 -0800
> From: Daniel Colascione <dancol@dancol.org>
> CC: nbtrap@nbtrap.com, 16413@debbugs.gnu.org
>
> Narrowing *is* generally useful for treating part of a buffer as a
> consistent unit, though, especially when that part is syntactically
> different from the rest of the buffer.
Not sure what you mean by "consistent unit".
From the ELisp manual:
30.4 Narrowing
==============
"Narrowing" means limiting the text addressable by Emacs editing
commands to a limited range of characters in a buffer. The text that
remains addressable is called the "accessible portion" of the buffer.
Perceiving and treating narrowing as something beyond that can,
indeed, cause conceptual and practical difficulties. For example,
narrowing the buffer in the middle of bidirectional context will most
of the time completely screw up the text on display.
next prev parent reply other threads:[~2014-01-11 8:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 3:05 bug#16413: 24.3.50; Inconsistent behavior of text property functions in narrowed buffer Nathan Trapuzzano
2014-01-11 4:05 ` Daniel Colascione
2014-01-11 4:09 ` Daniel Colascione
2014-01-11 12:20 ` Nathan Trapuzzano
2014-01-11 13:08 ` Eli Zaretskii
2014-01-11 13:52 ` Nathan Trapuzzano
2014-01-11 14:17 ` Eli Zaretskii
2014-01-11 19:43 ` Nathan Trapuzzano
2014-01-11 8:01 ` Eli Zaretskii
2014-01-11 8:03 ` Daniel Colascione
2014-01-11 8:12 ` Eli Zaretskii [this message]
2014-01-11 8:17 ` Daniel Colascione
2014-01-11 8:27 ` Eli Zaretskii
2014-01-12 3:42 ` Stefan Monnier
2014-01-12 4:35 ` Daniel Colascione
2014-01-12 15:53 ` Eli Zaretskii
2014-01-12 21:37 ` Stefan Monnier
2014-01-12 22:17 ` Nathan Trapuzzano
2014-01-13 4:01 ` Stefan Monnier
2014-01-13 4:04 ` Daniel Colascione
2014-01-13 4:21 ` Stefan Monnier
2014-01-13 12:09 ` Nathan Trapuzzano
2014-01-13 14:51 ` Stefan Monnier
2014-01-11 12:24 ` Nathan Trapuzzano
2014-01-11 13:05 ` Eli Zaretskii
2014-01-11 13:56 ` Nathan Trapuzzano
2014-01-11 14:18 ` Eli Zaretskii
2014-01-11 19:44 ` Nathan Trapuzzano
2014-01-11 19:58 ` Eli Zaretskii
2014-01-11 20:13 ` Nathan Trapuzzano
2014-01-11 20:27 ` Eli Zaretskii
2014-01-11 20:40 ` Nathan Trapuzzano
2014-01-11 20:46 ` Eli Zaretskii
2022-04-28 11:09 ` Lars Ingebrigtsen
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=834n5baqd2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16413@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=nbtrap@nbtrap.com \
/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.