From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Elisp help needed
Date: 01 Dec 1999 20:27:11 +0100 [thread overview]
Message-ID: <m3emd61my8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ycczow6uz2n.fsf@orff.sea.tera.com>
Ted Stern <stern@tera.com> writes:
> To deal with this, I want to modify one specific part of nndoc-type-alist,
> specifically, the article-begin section of slack-digest. I can handle the
> regular expressions but not the elisp. I know there is some combo of getcar,
> setcdr, etc. but I don't have a manual handy.
car, setcdr, setcar, cdr. And stuff. push is also nice.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-12-01 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-22 19:05 Ted Stern
1999-12-01 19:27 ` Lars Magne Ingebrigtsen [this message]
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=m3emd61my8.fsf@quimbies.gnus.org \
--to=larsi@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).