unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: juri@jurta.org, teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Problems with whole buffer Custom functions.
Date: Tue, 24 Jan 2006 22:28:37 -0500	[thread overview]
Message-ID: <E1F1bKn-0005cx-3S@fencepost.gnu.org> (raw)
In-Reply-To: <43D51ABB.9020802@gmx.at> (message from martin rudalics on Mon, 23 Jan 2006 19:04:43 +0100)

    Now change the face of `show-paren-match' to "turquoise" and that of
    `show-paren-mismatch' to "purple" and do C-_ twice again.  This time
    both modifications are undone.  Hence whether a modification can be
    undone may depend on whether this or another modification is the first
    editing change for a specific option.

Maybe the undo command needs to specialize to
the changes for the specific item.  Something like undo-in-region.

    The reason for this is that editing also changes some magic text from
    "STANDARD." to "EDITED, shown value does not take effect until you set
    or save it.".  This modification is, however, not recorded in
    `buffer-undo-list' and the buffer position recorded before editing
    started becomes invalid with respect to the actual buffer contents.

I guess the code that does these changes
ought to update the positions in the undo list also.

  reply	other threads:[~2006-01-25  3:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13  3:32 Problems with whole buffer Custom functions Luc Teirlinck
2006-01-17  1:27 ` Juri Linkov
2006-01-17  4:13   ` Luc Teirlinck
2006-01-17 21:54     ` Juri Linkov
2006-01-18  0:29       ` Kevin Rodgers
2006-01-23  0:10       ` Richard M. Stallman
2006-01-22  0:45     ` Juri Linkov
2006-01-22  1:46       ` Luc Teirlinck
2006-01-23  1:42         ` Juri Linkov
2006-01-24 16:46           ` Richard M. Stallman
2006-01-24 21:45             ` Juri Linkov
2006-01-24 23:11               ` Lennart Borgman
2006-01-25  7:55                 ` Juri Linkov
2006-01-25 15:45               ` Richard M. Stallman
2006-01-22  1:55       ` Luc Teirlinck
2006-01-23  1:43         ` Juri Linkov
2006-01-22  0:45     ` Juri Linkov
2006-01-22 17:44       ` Richard M. Stallman
2006-01-19 17:44   ` Richard M. Stallman
2006-01-22  0:45     ` Juri Linkov
2006-01-22 17:44       ` Richard M. Stallman
2006-01-22 21:28         ` Drew Adams
2006-01-23  1:47           ` Juri Linkov
2006-01-23  2:58             ` Drew Adams
2006-01-23  6:17               ` Juri Linkov
2006-01-24 16:47           ` Richard M. Stallman
2006-01-23  1:47         ` Juri Linkov
2006-01-24 16:46           ` Richard M. Stallman
2006-01-23 18:04         ` martin rudalics
2006-01-25  3:28           ` Richard M. Stallman [this message]
2006-01-22 17:44       ` Richard M. Stallman
  -- strict thread matches above, loose matches on Subject: below --
2006-01-25  8:58 LENNART BORGMAN

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=E1F1bKn-0005cx-3S@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=teirllm@dms.auburn.edu \
    /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).