From: Glenn Morris <rgm@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 5477@debbugs.gnu.org
Subject: bug#5477: 23.1.91; diary-unhide-everything sometimes doesn't
Date: Tue, 26 Jan 2010 15:21:32 -0500 [thread overview]
Message-ID: <eqaaw07h2r.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87fx5tuap4.fsf@escher.home>
Stephen Berman wrote:
> (defun diary-unhide-everything ()
> "Show all invisible text in the diary."
> (kill-local-variable 'diary-selective-display)
> ! (save-excursion
> ! (save-restriction
> ! (widen)
> ! (remove-overlays (point-min) (point-max) 'invisible 'diary)))
> (kill-local-variable 'mode-line-format))
This seems fine. Is your save-excursion really necessary?
next prev parent reply other threads:[~2010-01-26 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 21:38 bug#5477: 23.1.91; diary-unhide-everything sometimes doesn't Stephen Berman
2010-01-26 20:21 ` Glenn Morris [this message]
2010-01-26 21:05 ` Stephen Berman
2010-01-26 21:14 ` Glenn Morris
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=eqaaw07h2r.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=5477@debbugs.gnu.org \
--cc=stephen.berman@gmx.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).