all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: Miles Bader <miles@gnu.org>
Subject: Re: question about narrowed behavior of next-property-change et al.
Date: Sat, 25 Jan 2003 20:12:29 -0500	[thread overview]
Message-ID: <200301260112.h0Q1CTr17923@rum.cs.yale.edu> (raw)
In-Reply-To: E18cVtQ-0002g8-00@fencepost.gnu.org

>     Since the suggested change would only effect narrowed buffers, and only
>     to make them act more like a normal non-narrowed buffer, I would think
>     that only code that explicitly uses narrowing is potentially a problem
>     (under the assumption that a narrowed buffer should usually appear to
>     lisp code as if it were a normal buffer containing only the narrowed
>     region).
> 
> This reasoning is plausible indeed, but I still think that whoever
> changes this should also check the callers one buy one.

Instead of spending this time, I'd rather bet $1000 that Miles's change will
not introduce any new bug: it might make an existing bug show up more
often, but introducing a new bug with his suggested change seems incredibly
unlikely.


	Stefan

  reply	other threads:[~2003-01-26  1:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23  8:50 question about narrowed behavior of next-property-change et al Miles Bader
2003-01-23 16:12 ` Stefan Monnier
2003-01-24  5:43 ` Richard Stallman
2003-01-24  6:06   ` Miles Bader
2003-01-25 19:23     ` Richard Stallman
2003-01-26  1:12       ` Stefan Monnier [this message]
2003-01-27  2:31         ` Richard Stallman
2003-01-27 13:33           ` Stefan Monnier
2003-01-27 14:52             ` Miles Bader
2003-01-29  0:06               ` Richard Stallman

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=200301260112.h0Q1CTr17923@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=miles@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.