From: "Juanma Barranquero" <lekktu@gmail.com>
To: weber <hugows@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacsclient buffers
Date: Fri, 9 Feb 2007 17:49:32 +0100 [thread overview]
Message-ID: <f7ccd24b0702090849u3aadc3c6g65625971f3a6dec3@mail.gmail.com> (raw)
In-Reply-To: <1171038095.049533.257300@j27g2000cwj.googlegroups.com>
On 9 Feb 2007 08:21:35 -0800, weber <hugows@gmail.com> wrote:
> My question is: is there some variable that I can check to see if a
> buffer is regular or opened by emacsclient?
If emacsclient is waiting for a buffer to be edited, the buffer will
have a non-nil local variable `server-buffer-clients'.
/L/e/k/t/u
next prev parent reply other threads:[~2007-02-09 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:21 Emacsclient buffers weber
2007-02-09 16:49 ` Juanma Barranquero [this message]
[not found] ` <mailman.4242.1171039778.2155.help-gnu-emacs@gnu.org>
2007-02-09 16:54 ` weber
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=f7ccd24b0702090849u3aadc3c6g65625971f3a6dec3@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=hugows@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).