From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: lost argument and doc string
Date: Mon, 11 Feb 2002 21:37:40 +0200 [thread overview]
Message-ID: <4634-Mon11Feb2002213740+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <20020211173214.3AA9.LEKTU@terra.es> (message from Juanma Barranquero on Mon, 11 Feb 2002 17:34:14 +0100)
> From: Juanma Barranquero <lektu@terra.es>
> Date: Mon, 11 Feb 2002 17:34:14 +0100
>
> > Is it possible that the change in the way doc strings are put in C files
> > confuses the Windows port, either the make-docfile program or Emacs
> > itself?
>
> Maybe, but then why some docstrings can be seen just fine?
Because some doc strings come from Lisp files?
But that's a stab in the dark; it would be nice if someone could step
with a debugger through the offending code and see what's going on
there.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-11 19:37 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 [this message]
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
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=4634-Mon11Feb2002213740+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.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.
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).