buttonize creates many many buttons

buttonize creates many many buttons

[Eric S Fraga]

[-- 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)

Re: buttonize creates many many buttons

[Lars Ingebrigtsen]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> 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).

Gnus is doing org-mode dissection, too, and treating these as pseudo
MIME parts.  So you'll get a lot of buttons.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: buttonize creates many many buttons

[Julien Danjou]

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

On Sun, Feb 06 2011, Eric S Fraga wrote:

> 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).

I get many buttons with your message too. Looks like a bug to me. :(

-- 
Julien Danjou
❱ http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: buttonize creates many many buttons

[Eric S Fraga]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> 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).
>
> Gnus is doing org-mode dissection, too, and treating these as pseudo
> MIME parts.  So you'll get a lot of buttons.

Okay, that makes sense.  Is there an easy way (or any way at all that
doesn't involve looking at the raw message) to extract such a text file,
that has been dissected, in one piece?  Or can I turn off (disable) the
org dissection process temporarily?

Thanks,
Eric
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 + No Gnus v0.11

Re: buttonize creates many many buttons

[Lars Ingebrigtsen]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Okay, that makes sense.  Is there an easy way (or any way at all that
> doesn't involve looking at the raw message) to extract such a text file,
> that has been dissected, in one piece? 

I think `C-d' is the easiest way.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen