Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: parts with new page (Ctrl-L) characters
Date: 08 Dec 1998 11:39:37 -0600	[thread overview]
Message-ID: <wkyaoittwm.fsf@chevax.ecs.umass.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]


Here is an interesting example.  The attached file has a new page character
in it (Ctrl-L).  As a result, the normal display (without buttons) has a
"next page" sensitive area.  This area is NOT a button, but just sensitive
text.  

To make this even more interesting, turn on the buttons and try to hide the
rich text.  When I do it on a normal section of text/plain the entire text
is hidden.  When I push the button on a section with a new page in it,
NOTHING is hidden.  I do get the ellipses that suggests something went
away.  If I "unhide" by hitting the button again, I am shown the Ctrl-L
instead of it giving me a page break.  

Even though it shows me the Ctrl-L, there is now a "Next Page" spot that
takes me to a page with all of the text in it and ANOTHER "next page" spot.
This one takes me to the rest of the document.



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Example with new page --]
[-- Type: text/richtext, Size: 264 bytes --]

Content-Type: text/enriched
Text-Width: 75

Testing

<bold>This is bold</bold><italic>

This is italic</italic>

\f<underline>This is underlined</underline>

<underline><italic><bold>This is bold, italic and underlined!</bold></italic></underline>

Back to normal


[-- Attachment #3: Type: text/plain, Size: 162 bytes --]


-- 
Jack Vinson <jvinson@chevax.ecs.umass.edu>    http://www.cis.upenn.edu/~vinson/
Zippy: All this time I've been VIEWING a RUSSIAN MIDGET SODOMIZE a HOUSECAT!

             reply	other threads:[~1998-12-08 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-08 17:39 Jack Vinson [this message]
1998-12-13  8:22 ` Lars Magne Ingebrigtsen

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=wkyaoittwm.fsf@chevax.ecs.umass.edu \
    --to=jvinson@chevax.ecs.umass.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).