Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: can't see lisp attachments.
Date: Fri, 18 Mar 2022 19:16:55 +0100	[thread overview]
Message-ID: <87sfrfxh0o.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87fsnfb0uv.fsf@mat.ucm.es>

Uwe writes:

> Now I don't see any attachment, only if I run gnus-article-save-part the
> attachment appears (it is also shown in other email readers).
>
> So which variables control the display of attachments?

One that you have changed; it is shown in my Gnus:

    From: Arash Esbati <arash@gnu.org>
    Subject: Updating algpseudocode.el
    Newsgroups: gmane.emacs.auctex.devel
    To: Uwe Brauer <oub@mat.ucm.es>
    Cc: auctex-devel <auctex-devel@gnu.org>
    Date: Fri, 18 Mar 2022 11:28:19 +0100 (7 hours, 39 minutes, 48 seconds ago)
    Attachment: [2. application/emacs-lisp; algpseudocode.el]...

    Hi Uwe,

    you may have seen that I've added some code to AUCTeX in order to handle
    indentation of conditionals.  One side effect is that now we can indent
    the contents in algorithmic environment (provided by algpseudocode.sty)
    better.  I plan to change that style like attached.  I did some brief
    testing and it seems to work.  Do you mind update your AUCTeX repo,
    install this file in your private style directory and give it a roll?

    TIA.  Best, Arash

    [2. application/emacs-lisp; algpseudocode.el]...


And also in a Gnus with no configuration set up what so ever.


  Best regards,

    Adam

-- 
 "Happiness isn't good enough for me! I demand              Adam Sjøgren
  euphoria!"                                           asjo@koldfront.dk



  reply	other threads:[~2022-03-18 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 17:56 Uwe Brauer
2022-03-18 18:16 ` Adam Sjøgren [this message]
2022-03-18 18:22 ` Eric S Fraga
2022-03-19  8:13   ` Uwe Brauer
2022-03-19  8:51   ` [SOLVED] (was: can't see lisp attachments.) Uwe Brauer

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=87sfrfxh0o.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).