Gnus development mailing list
 help / color / mirror / Atom feed
From: gsstark@MIT.EDU (Greg Stark)
Subject: Re: hidden citation button gotchas
Date: 08 Mar 1996 17:07:28 -0500	[thread overview]
Message-ID: <ycqlolbb5nj.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: gnus-bug@ifi.uio.no's message of 08 Mar 1996 20:35:21 +0100


The more i use Gnus, the more i get suspicious of its use of text properties
to hide headers, cited text, and signatures.  My uneasiness comes from the way
i can copy and paste text from the article and never know that i copied
the hidden text until i either save and reopen a file, or until i post news i
see the posting.  i think this is really dangerous and not in line with the
principle of least-surprise. 

There are two other possible implementations, one is too actually remove the
hidden text, the other is to use overlays instead of text properties.  With
overlays it would be possible to hide the hidden text and insert [...] buttons
without actually changing the text, so if you copied the text to another
buffer all the [...] and -- buttons would be magically transformed to the
hidden text as soon as you pasted, instead of later.  If you used the overlay
property after-text then the resulting text would even be free of extraneous
buttons.   This overlay solution  would solve the supercite problem of
inserting cited text with buttons and hidden text instead of the original.


--
greg


       reply	other threads:[~1996-03-08 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ycqag23xcyy.fsf@lola-granola.MIT.EDU>
     [not found] ` <w8senr4a8ee.fsf@hler.ifi.uio.no>
     [not found]   ` <ycqpwaobiu4.fsf@fierce-bad-rabbit.MIT.EDU>
     [not found]     ` <x6ohq7a09x.fsf@eyesore.no>
1996-03-08 22:07       ` Greg Stark [this message]
1996-03-09 22:56         ` 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=ycqlolbb5nj.fsf@fierce-bad-rabbit.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).