From: Sacha Chua <sacha@free.net.ph>
Subject: Re: Keeping a group visible.dormant doesn't
Date: Sun, 01 Jun 2003 21:26:59 +0800 [thread overview]
Message-ID: <87ptlydj30.fsf@sacha.mine.nu> (raw)
In-Reply-To: <m3k7c6k8jn.fsf@sbcglobal.net> (Harry Putnam's message of "Sat, 31 May 2003 16:20:28 -0700")
Harry Putnam <reader@newsguy.com> writes:
> I seem to recall being able to keep a group visible in Group buffer
> simply by ticking something (?) dormant. Then an asterisk appeared on
If you want to keep a group visible, you can add (visible . t) to its
group parameters. From the *Group* buffer, type "G p". If the group
parameter is nil, replace it with ((visible . t)), else add (visible .
t) to the list.
That's probably not what you meant, but it might be useful. =)
--
Sacha Chua <sacha@free.net.ph> - Ateneo CS faculty geekette
interests: emacs, gnu/linux, wearables, teaching compsci
http://richip.dhs.org/~sachac/
prev parent reply other threads:[~2003-06-01 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 23:20 Keeping a group visible.. dormant doesn't Harry Putnam
2003-06-01 9:07 ` Robert Epprecht
2003-06-01 13:26 ` Sacha Chua [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ptlydj30.fsf@sacha.mine.nu \
--to=sacha@free.net.ph \
/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 NNTP newsgroup(s).