From: Greg Stark <gsstark@MIT.EDU>
Subject: spoiler warnings, "next page" buttons, washing functions
Date: 18 Apr 1996 18:50:13 -0400 [thread overview]
Message-ID: <ycqviixkuze.fsf@mit.edu> (raw)
So i've just started reading a newsgroup with spoiler warnings.
Spoiler warnings are there to prevent people from reading things that
spoil future episodes of a tv show or a movie; things like
``Rosebud was his ______'' or the ``Maltese Falcon was ______''
The spoiler warnings usually consist of some subset of a few ^L's lots of
blank lines, etc. Gnus does pretty cool things with them, but not really cool
enough. If there are multiple ^L's the i have to hit SPC several times to get
to the message; if there are 25 blank lines then lots of screen real-estate is
wasted; sometimes the spoiler space is quoted with >'s and it gets hidden as a
citation.
What i want is for Gnus to treat any sequence or combination of the following
as a single spoiler warning and hide it all, replacing it with a "Next Page"
button:
^L's
more than n blank lines
more than m identical lines
(which should be replaced with button to show them)
any whitespace surrounding any of the above
greg
reply other threads:[~1996-04-18 22:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ycqviixkuze.fsf@mit.edu \
--to=gsstark@mit.edu \
/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).