From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: gnus mailing list <ding@gnus.org>
Subject: buttonize creates many many buttons
Date: Sun, 06 Feb 2011 15:46:10 +0000 [thread overview]
Message-ID: <87tyghp3nh.fsf@ucl.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
Hello,
I am trying to understand how =gnus-summary-display-buttonized= works or
is intended to work. If I attach an inline text file, of type
text/orgmode, as I have here:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: example org file with demonstraing a bug in list handling --]
[-- Type: text/orgmode, Size: 870 bytes --]
# -*- coding: utf-8; -*-
#+TITLE: examplebug.org
#+AUTHOR: Eric S Fraga
#+EMAIL: e.fraga@ucl.ac.uk
#+OPTIONS: H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil
#+latex_header: \usepackage{tikz}
* latex code block within list
1. I have a list
2. with several items
3. and then one of them includes some latex:
#+begin_latex
\begin{tikzpicture}[x=2cm,y=2cm]
\draw [red] (0,0) -- (2,2);
\end{tikzpicture}
#+end_latex
4. subsequent list items start a new list
5. if we include some html
#+begin_html
<img src="mip.png" alt="Mixed integer programming">
#+end_html
6. that works fine.
7. if we include a babel code block
#+begin_src octave :exports code :var x=20
3*x+5
#+end_src
#+results:
: 65
8. that also works just fine.
[-- Attachment #3: Type: text/plain, Size: 711 bytes --]
when I look at this message, the text comes out perfectly fine inline.
However, I may want to save this attachment so I figured that displaying
it buttonized was the way to go. When I do that (K b), I get a very
large number (10-12?) of buttons for that file! The buttonizing
procedure seems to break the text file up a random locations (well, I
assume they are not really random but I see no apparent logic at first
glance).
Two questions:
1. is gnus-summary-display-buttonized the right function to use?
2. what is the logic behind the buttonizing procedure?
Thanks,
eric
PS - I know I can simply go to the raw message and extract the text that
way but...
--
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)
next reply other threads:[~2011-02-06 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 15:46 Eric S Fraga [this message]
2011-02-07 9:48 ` Lars Ingebrigtsen
2011-02-07 18:53 ` Eric S Fraga
2011-02-14 2:49 ` Lars Ingebrigtsen
2011-02-07 10:06 ` Julien Danjou
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=87tyghp3nh.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).