From: Ryan Yeske <rcyeske@gmail.com>
Subject: Re: with-current-buffer mystery
Date: Fri, 26 Nov 2004 04:38:36 GMT [thread overview]
Message-ID: <87sm6xut3k.fsf@cut.hotdog.tmp> (raw)
In-Reply-To: yoij3byy3wv1.fsf@eorl.dd.chalmers.se
bojohan+news@dd.chalmers.se (Johan Bockgård) writes:
> Ryan Yeske <rcyeske@gmail.com> writes:
>
> > When I eval the following expressions, I found that it seems to
> > depend on whether or not the buffer is visible.
> [...]
> > Any help or explanations would be greatly appreciated.
>
> (info "(elisp)Window Point")
Thanks, Johan. This is what I was missing.
Ryan
prev parent reply other threads:[~2004-11-26 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 7:57 with-current-buffer mystery Ryan Yeske
2004-11-25 13:02 ` Johan Bockgård
2004-11-26 4:38 ` Ryan Yeske [this message]
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=87sm6xut3k.fsf@cut.hotdog.tmp \
--to=rcyeske@gmail.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.
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).