From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: shr-map keymap issues
Date: Mon, 02 May 2011 12:22:38 -0500 [thread overview]
Message-ID: <877ha9vwyp.fsf@lifelogs.com> (raw)
In-Reply-To: <m3bozlgh0j.fsf@quimbies.gnus.org>
On Mon, 02 May 2011 19:16:12 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
LMI> Anyway, I think -show-source just copies the `C-g' keystroke, but in a
LMI> less standard fashion.
>>
>> Can you explain how `C-g' views the source? I thought it viewed the raw
>> article, which is not the same thing.
LMI> What's the difference? :-)
MIME parts != whole article, and you're assuming shr will only ever be
used on articles. The former is the bigger problem, since decoding MIME
can get tedious.
Also it's nice to just write out the "view source" buffer to a HTML file
directly without editing out the headers, so even when article == HTML
content it's a convenient shortcut.
LMI> So perhaps having -mini-help would make sense, since there are so many
LMI> new shr-related button commands...
OK then. Take my defun for it if you like.
>>>> 2) `i' and `I' are OK, but we should also have a way to hide images and
>>>> to copy their URL. It would be nice to also provide "insert all images"
>>>> and "hide all images".
>>
LMI> There's Gnus-level functions to do that, isn't there?
>>
>> I don't see them in `C-h m' or any of the menus.
LMI> `W D W' and `W D D' (hide-/show-images).
OK. So we still need a way to copy the url, right?
>>>> 5) `+' and `-' should expand and collaps the current element.
>>
LMI> Collapse/expand how?
>>
>> Like Outline mode for example.
LMI> I don't use outline mode, so I don't really know what that would do on
LMI> an HTML article.
LMI> You're supposed to read the article, and possibly push a few buttons.
LMI> Collapsing "elements" sounds like something you'd do in an editing
LMI> mode.
OK, it's like an accordion then ;) And like that instrument, it's
mostly useless so never mind.
Ted
next prev parent reply other threads:[~2011-05-02 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 18:58 Ted Zlatanov
2011-04-22 0:14 ` Ted Zlatanov
2011-05-01 16:13 ` Lars Magne Ingebrigtsen
2011-05-02 17:07 ` Ted Zlatanov
2011-05-02 17:16 ` Lars Magne Ingebrigtsen
2011-05-02 17:22 ` Ted Zlatanov [this message]
2011-05-30 20:58 ` Lars Magne Ingebrigtsen
2011-05-31 16:31 ` Ted Zlatanov
2011-05-31 19:00 ` Lars Magne Ingebrigtsen
2011-05-31 19:18 ` Ted Zlatanov
2011-05-31 19:26 ` Lars Magne Ingebrigtsen
2011-05-03 20:53 ` Ted Zlatanov
2011-05-06 9:21 ` Katsumi Yamaoka
2011-05-09 15:21 ` Ted Zlatanov
2011-05-10 0:12 ` Katsumi Yamaoka
2011-05-30 20:59 ` Lars Magne Ingebrigtsen
2011-05-01 16:10 ` 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=877ha9vwyp.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).