unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "N. Raghavendra" <raghu@mri.ernet.in>
Subject: Re: elisp question
Date: 02 Dec 2005 13:14:07 +0530	[thread overview]
Message-ID: <86psogj648.fsf@riemann.mri.ernet.in> (raw)
In-Reply-To: 7er78w4c9t.fsf@ada2.unipv.it

At 2005-12-02T00:40:14+01:00, Thien-Thi Nguyen wrote:

> fyi, the emacs lisp reference manual in cvs emacs, node "Bindat
> Examples", has code that does cookie file composition and extraction
> in elisp (i.e., emulating the common-case behaviors of fortune(1)
> and strfile(8), rendering them unnecessary).

Thank you for the information.  I checked out the Emacs Lisp manual
from CVS, and saw the examples.  Since I use Emacs 21.3, I checked out
`bindat.el' from CVS, and tried the examples from the manual.  They
function perfectly.

There seems to be some incompatibility between the index files created
from the same fortune file by strfile(8) and `fcookie-create-index'.
In particular, if I create an index file with `fcookie-create-index'
and apply fortune(1) to it, I sometimes get the first cookie in the
file, or no cookie at all.  OTOH, the same index file works well with
`fcookie'.

Similarly, if I create an index file with strfile(8) and evaluate
`fcookie' on the corresponding cookie file, a buffer containing the
entire cookie file is displayed.

Raghavendra.

-- 
N. Raghavendra <raghu@mri.ernet.in> | See message headers for contact
Harish-Chandra Research Institute   | and OpenPGP details.

  reply	other threads:[~2005-12-02  7:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 23:13 elisp question Tim McNamara
2005-11-30 23:22 ` Lennart Borgman
2005-12-01  5:07 ` Stefan Monnier
2005-12-01 19:29   ` Tim McNamara
2005-12-01 21:00     ` Stefan Monnier
2005-12-02  1:02       ` Tim McNamara
2005-12-02 17:51   ` Kevin Rodgers
2005-12-01  6:24 ` N. Raghavendra
2005-12-01 19:32   ` Tim McNamara
2005-12-01 21:37     ` N. Raghavendra
2005-12-01 23:40       ` Thien-Thi Nguyen
2005-12-02  7:44         ` N. Raghavendra [this message]
2005-12-02 14:43           ` Thien-Thi Nguyen
2005-12-02  1:05       ` Tim McNamara
     [not found] ` <mailman.17404.1133392955.20277.help-gnu-emacs@gnu.org>
2005-12-01 19:25   ` Tim McNamara
  -- strict thread matches above, loose matches on Subject: below --
2009-09-27 14:32 Elisp Question magicus
2009-09-27 15:26 ` Giorgos Keramidas
2009-09-27 17:10   ` magicus
     [not found] <mailman.941.1223918781.25473.help-gnu-emacs@gnu.org>
2008-10-13 18:11 ` elisp question Niels Giesen
2008-10-13 19:09   ` Seweryn Kokot
     [not found]   ` <mailman.948.1223924333.25473.help-gnu-emacs@gnu.org>
2008-10-13 19:40     ` Pascal J. Bourguignon
2008-10-13 20:47       ` Drew Adams
2008-10-13 21:11       ` Seweryn Kokot
2008-10-13 17:36 Seweryn Kokot
2008-04-30 21:23 harven
2008-05-01 13:08 ` Kevin Rodgers
     [not found] ` <mailman.11020.1209647315.18990.help-gnu-emacs@gnu.org>
2008-05-01 13:54   ` harven
2008-05-03 15:38 ` Bastien
2003-08-20  7:37 Mike Ballard
2003-08-20  8:07 ` Joakim Hove
2003-08-22  5:52   ` Mike Ballard
2003-08-22  6:38     ` Joakim Hove
2003-08-20 15:07 ` Peter Lee

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86psogj648.fsf@riemann.mri.ernet.in \
    --to=raghu@mri.ernet.in \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).