From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: can't see lisp attachments.
Date: Sat, 19 Mar 2022 09:13:16 +0100 [thread overview]
Message-ID: <87pmmicqcj.fsf@mat.ucm.es> (raw)
In-Reply-To: <871qyz6rza.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 4998 bytes --]
>>> "ESF" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Friday, 18 Mar 2022 at 18:56, Uwe Brauer wrote:
>> I just received an email from the auctex list, that looks in my setting
>> as follows
> You might need to show us the full (raw) email to see what is going on?
> Maybe what "C-u g" shows?
Good point: here is the result of that, so I have to check the
content-type most likely
Uwe
Delivered-To: oub@mat.ucm.es
Received: by 2002:a17:906:8d7:0:0:0:0 with SMTP id o23csp1264156eje; Fri, 18
Mar 2022 03:29:57 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJwYhg62Bbk2T/8rBak8xtEtIAJYVyugKOUyMGljqR+cWolZcgkaYt8TiMkHLjOFtisLxtTC
X-Received: by 2002:a05:620a:1241:b0:67d:2c16:3800 with SMTP id
a1-20020a05620a124100b0067d2c163800mr5255125qkl.3.1647599396705; Fri, 18 Mar
2022 03:29:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1647599396; cv=none; d=google.com;
s=arc-20160816;
b=F/06hA2MkdOExvoJT3o9Q2EvfWjGvfaVvLfA8M4srjiXoHJtXMpfjAp9EErop5PVs6
uet6buYeJ2Pn0ZNow7tO5TSwl0rfyZOlSC8dYDHhuWDk8T8IzdR2QqCb221rGKAgLLZe
d2jP0d31POVg8X89fuMNT/F/KI2VxB7l/bt0h8dHbsYSM8kBKFxh06jsDB3t8SWOTu9N
eexFAGq/YU2mSLOz1UBvFwqjNtL6Nz42b33JRItxXBFFphdQVG6opF/I7bSzeuiXdTgk
RCDS/h4QQm6AQ0lW7CpvLP9/mW4YknSrtjtmvh5SLFwQqpDJ5SiKpXUqlHjYuxkLKzLF cS6g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=arc-20160816; h=mime-version:user-agent:message-id:date:subject:cc:to:from
:dkim-signature; bh=SB9l4CN+AI6JROUGzJttNXqOeQAH1+AUvFv0u/eboZ8=;
b=DYzesxXIXdoHTzk4ik6uhaTyXm58a9OJEu2IiD4R0FHkg1DSC+H2/dAz3tY9pS4mWy
W9OpzHVKuNmXuyIHnaMSdxbsqAD/PFeLnc0NR65KH1MBq77dUObYDDsFRXGnz4M7L0wQ
fldfPvSxK+ljTGohJPVkZUfmrFcsfAVyVc/IzIfNPh4j8XH1apLH5tEbegqvATrJc27U
8+YA7SAuj9640yvCRMTbscrOWc73jZ9z2wY7oK3EuWLbSX/bTdjVDg58uge88OO64SxF
ZlE9hD8RSrIQO9or/FQcHQCJDaG7MPmcdc1nQKFMhcoisn4MiNLXVss3Fn/1o6X2rvot enVg==
ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gnu.org
header.s=fencepost-gnu-org header.b=mTLpt0KF; spf=pass (google.com: domain of
arash@gnu.org designates 209.51.188.92 as permitted sender)
smtp.mailfrom=arash@gnu.org; dmarc=pass (p=NONE sp=NONE dis=NONE)
header.from=gnu.org
Return-Path: <arash@gnu.org>
Received: from eggs.gnu.org (eggs.gnu.org. [209.51.188.92]) by mx.google.com
with ESMTPS id
ay39-20020a05620a17a700b0067d9681c6edsi2031253qkb.543.2022.03.18.03.29.56 for
<oub@mat.ucm.es> (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305
bits=256/256); Fri, 18 Mar 2022 03:29:56 -0700 (PDT)
Received-SPF: pass (google.com: domain of arash@gnu.org designates
209.51.188.92 as permitted sender) client-ip=209.51.188.92;
Authentication-Results: mx.google.com; dkim=pass header.i=@gnu.org
header.s=fencepost-gnu-org header.b=mTLpt0KF; spf=pass (google.com: domain of
arash@gnu.org designates 209.51.188.92 as permitted sender)
smtp.mailfrom=arash@gnu.org; dmarc=pass (p=NONE sp=NONE dis=NONE)
header.from=gnu.org
Received: from [2001:470:142:3::e] (port=57062 helo=fencepost.gnu.org) by
eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim
4.90_1) (envelope-from <arash@gnu.org>) id 1nV9rn-00050u-HT; Fri, 18 Mar 2022
06:29:55 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
s=fencepost-gnu-org; h=MIME-Version:Date:Subject:To:From:in-reply-to:
references; bh=SB9l4CN+AI6JROUGzJttNXqOeQAH1+AUvFv0u/eboZ8=; b=mTLpt0KFj/94mr
uxoZzdaPCC7E6qF5cDZwlCintH+yMiNbRv9lHDrIKa3S6bdLTjSnybXnDqx3rGq1Fnx3NUzlWUFY+
lJtMzPKIVIbVDCmd5qX55vMbMPwc6eFesOKott+asdLx4xBX0SKf2uhfMT07vGWtJcV046yuLw17Q
jB/jaghTfSe2U4hrUz9/361GOy7hMs78SjvmI93bfZikJR7uMCo6nsK/w7tP54l+lxAyCPKpwIaR1
bl4dgJVc5qdM8biXVR5XMNZnevSIqXDPrI+N/Oh17YZH9Iq2wwf0amg6NHIkPRnefxN7Ck0fLJUvc
k5CduwGLmFuRVxgH5x7g==;
Received: from p5b326363.dip0.t-ipconnect.de ([91.50.99.99]:62857 helo=MUTANT)
by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.90_1) (envelope-from <arash@gnu.org>) id 1nV9rn-0005WJ-3Y; Fri, 18
Mar 2022 06:29:55 -0400
From: Arash Esbati <arash@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: auctex-devel <auctex-devel@gnu.org>
Subject: Updating algpseudocode.el
Date: Fri, 18 Mar 2022 11:28:19 +0100
Message-ID: <868rt7ftbw.fsf@gnu.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
--=-=-=
Content-type: text/plain
Content-transfer-encoding: 7bit
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
--=-=-=
Content-type: application/emacs-lisp
Content-transfer-encoding: quoted-printable
--=-=-=--
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-03-19 8:13 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
2022-03-18 18:22 ` Eric S Fraga
2022-03-19 8:13 ` Uwe Brauer [this message]
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=87pmmicqcj.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).