unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: jasonr@gnu.org, lektu@terra.es, emacs-devel@gnu.org, andrewi@gnu.org
Subject: Re: lost argument and doc string
Date: Wed, 13 Feb 2002 07:43:56 +0200 (IST)	[thread overview]
Message-ID: <Pine.SUN.3.91.1020213074011.13847A@is> (raw)
In-Reply-To: <20020212.114825.01368903.Takaaki.Ota@am.sony.com>


On Tue, 12 Feb 2002, Tak Ota wrote:

> I did the same experiment, running make-docfile manually on simple.el,
> and got surprised.  And the source file is requesting the sequence
> `dquote bslash newline' as the beginning of the valid doc string in
> case of el files.  I don't think this is right.  Starting doc string
> that way is only optional I believe.

Please make sure that any changes you make in this don't break 
loaddefs.el.  I believe loaddefs is the reason for that requirement of 
how the doc string should begin (since loaddefs is generated by a 
program, there's no problem satisfying that requirement in that case).  I 
imagine that there was some reason to require such a format, in which 
case we should avoid breaking that.

Richard, do you recall why this format was required?

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-02-13  5:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10  6:59 lost argument and doc string Tak Ota
2002-02-10 17:08 ` Eli Zaretskii
2002-02-10 17:32   ` Pavel Janík
2002-02-10 23:28     ` Tak Ota
2002-02-11  5:48       ` Pavel Janík
2002-02-11  5:48       ` Eli Zaretskii
2002-02-11 16:34         ` Juanma Barranquero
2002-02-11 19:37           ` Eli Zaretskii
2002-02-12  2:32             ` Tak Ota
2002-02-12  8:35               ` Eli Zaretskii
2002-02-12 14:23                 ` Tak Ota
2002-02-12 18:57                   ` Jason Rumney
2002-02-12 19:48                     ` Tak Ota
2002-02-13  5:43                       ` Eli Zaretskii [this message]
2002-02-13  6:01                         ` Tak Ota
2002-02-13 13:40                         ` Andreas Schwab
2002-02-13 14:23                           ` Eli Zaretskii
2002-02-13 19:50                       ` Jason Rumney
2002-02-13 20:22                         ` Tak Ota
2002-02-13 21:02                           ` Jason Rumney
2002-02-14  7:36                             ` Tak Ota
2002-02-15 10:36                               ` Richard Stallman
2002-02-15 20:36                                 ` Tak Ota
2002-02-13 21:00                         ` Tak Ota
2002-02-14  3:11                     ` Richard Stallman
2002-02-14 15:13                       ` Tak Ota
2002-02-13 15:37                 ` Richard Stallman
2002-02-11 18:48       ` Richard Stallman

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=Pine.SUN.3.91.1020213074011.13847A@is \
    --to=eliz@is.elta.co.il \
    --cc=andrewi@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=lektu@terra.es \
    /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).