unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: reading/writing binary data in structured form
Date: Mon, 28 Apr 2008 10:38:03 -0400	[thread overview]
Message-ID: <jwv4p9mgi7v.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <uabjezmq7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 28 Apr 2008 06:23:28 +0300")

>> >> Kim, is there a reason not to make bindat-pack and bindat-unpack
>> >> autoloaded?
>> 
>> > Only that I envisioned that people would explicitly require bindat
>> > if they need the features it provides.
>> 
>> Indeed.  It doesn't seem to make much sense to autoload part of it.

> Yes, but can it hurt?  We could put comments there explaining the
> reasons, in case at some point in the future doing so for the sake of
> documentation search will not be necessary.

It's not very satisfactory.  Maybe we should simply mention the package
in the lispref.

>> Maybe we should begin by improving the C-h p answer.
> I'm for it, but IMHO "C-h p" cannot be a precise tool, because it is
> based on too small amount of info (a few keywords), whereas
> apropos-documentation has much more to play with.

I don't think it "cannot be a precise tool" much more than C-h i cannot
be a precise tool.  But I agree that it requires a non-trivial amount
of work.  It would be worthwhile, tho.


        Stefan




      reply	other threads:[~2008-04-28 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 14:05 reading/writing binary data in structured form Werner LEMBERG
2008-04-26 15:25 ` Eli Zaretskii
2008-04-26 22:44   ` Werner LEMBERG
2008-04-27  3:12     ` Eli Zaretskii
2008-04-27  7:05       ` Werner LEMBERG
2008-04-27 15:55         ` Eli Zaretskii
2008-04-27 22:37           ` Kim F. Storm
2008-04-28  1:29             ` Stefan Monnier
2008-04-28  3:23               ` Eli Zaretskii
2008-04-28 14:38                 ` Stefan Monnier [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

  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=jwv4p9mgi7v.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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