From: Carsten Dominik <dominik@_DROP_THIS_science.uva.nl>
Subject: Re: invisible buffer is it possible?
Date: 26 Nov 2002 14:13:00 +0100 [thread overview]
Message-ID: <qzuel98pj8j.fsf@sand.science.uva.nl> (raw)
In-Reply-To: vflm3gjyeh.fsf@rpc71.cs.man.ac.uk
How about starting the buffer name with a space?
From the elisp documentation:
Buffers that are ephemeral and generally uninteresting to the user
have names starting with a space, so that the `list-buffers' and
`buffer-menu' commands don't mention them. A name starting with space
also initially disables recording undo information; see *Note Undo::.
- Carsten
>>>>> "PL" == Phillip Lord <p.lord@russet.org.uk> writes:
PL> I'm just wondering whether I can create an invisible buffer, or
PL> something similar? That is one which does not appear in the buffer
PL> menu list, and you can't accidentally change to.
PL> The reason for this is that I have use this little hack....
PL> (add-hook 'xml-mode-hook
PL> 'phil-psgml-hook)
PL> (defun phil-psgml-hook()
PL> "Does various checks and sets up various variables
PL> 1) Checks to see if the file being loaded is one which needs a fake DOCTYPE.
PL> That is I don't want to have the doctype in the buffer but want psgml mode to
PL> think that there is one.
PL> 2) Sets up default validate command"
PL> (interactive)
PL> (if (string= "build.xml"
PL> (file-name-nondirectory (buffer-file-name)))
PL> (setq sgml-parent-document '( "~/emacs/anthead.xml" "" "project"
PL> ))))
PL> What this does is allow me to use a DTD for editing ant build files,
PL> without having to put the doctype declaration into the build file
PL> itself, which goes into the anthead.xml file.
PL> However it results in the anthead.xml file being opened into a buffer,
PL> and it's just an annoyance.
PL> Is there someway that I can mark it invisible?
PL> Cheers
PL> Phil
next prev parent reply other threads:[~2002-11-26 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 12:41 invisible buffer is it possible? Phillip Lord
2002-11-26 13:13 ` Carsten Dominik [this message]
2002-11-26 14:12 ` Stein A. Stromme
2002-11-26 14:15 ` Stein A. Stromme
2002-11-26 15:15 ` Stefan Monnier <foo@acm.com>
2002-11-26 15:33 ` Phillip Lord
2002-11-26 15:44 ` lawrence mitchell
2002-11-26 16:17 ` Phillip Lord
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=qzuel98pj8j.fsf@sand.science.uva.nl \
--to=dominik@_drop_this_science.uva.nl \
/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).