unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lynn Winebarger <owinebar@gmail.com>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Docstring hack
Date: Sat, 30 Jul 2022 19:43:38 +0300	[thread overview]
Message-ID: <831qu25z5x.fsf@gnu.org> (raw)
In-Reply-To: <CAM=F=bBk=agYYTT+YCvgD8aM93VVP1NrERFCh1ApuaS9QgwLjQ@mail.gmail.com> (message from Lynn Winebarger on Sat, 30 Jul 2022 12:32:27 -0400)

> From: Lynn Winebarger <owinebar@gmail.com>
> Date: Sat, 30 Jul 2022 12:32:27 -0400
> Cc: luangruo@yahoo.com, emacs-devel <emacs-devel@gnu.org>
> 
>  Does this happen with any package we actually preload via loadup.el?
> 
> If you're not going to support using site-load except in the most trivial of ways, then you should say that in the
> documentation.

Did I say that we are not going to support this?

I asked an informative question, with the purpose of figuring out how
urgent it is for us to fix this issue.  Do I really deserve a cold
shower for asking such questions?

> But if you're not going to be willing to take up such bug fixes on some general principle (that I don't
> understand in a free software project), that would be useful to know.

I didn't say that, either.  And I couldn't really give any specific
answer to such a general question, because it depends on what kinds of
bugs and in which parts of the code you will report.  I could only
answer such question on a case by case basis.

> Personally, I am going to proceed with the last option (the fifth)

TBH I don't really understand your 5 alternatives, because you are
alluding to symbols I cannot find in the sources: I see neither
read_literal_string nor dynamic-docstring.  Are those typos or am I
blind?



  reply	other threads:[~2022-07-30 16:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 12:14 Docstring hack Lynn Winebarger
2022-07-30 12:25 ` Po Lu
2022-07-30 12:50   ` Lynn Winebarger
2022-07-30 13:04     ` Lynn Winebarger
2022-07-30 13:32     ` Po Lu
2022-07-30 13:28 ` Eli Zaretskii
2022-07-30 13:36   ` Po Lu
2022-07-30 15:11     ` Eli Zaretskii
2022-07-30 15:38       ` Lynn Winebarger
2022-07-30 15:44         ` Eli Zaretskii
2022-07-30 16:32           ` Lynn Winebarger
2022-07-30 16:43             ` Eli Zaretskii [this message]
2022-07-31  2:17               ` Po Lu
2022-07-31  6:27                 ` Eli Zaretskii
2022-07-31  7:24                   ` Po Lu
2022-07-31  7:56                     ` Eli Zaretskii
2022-07-31  8:48                       ` Po Lu
2022-07-31  9:14                         ` Lars Ingebrigtsen
2022-07-31 22:31                           ` Stefan Monnier
2022-08-01 10:38                             ` Lars Ingebrigtsen
2022-08-04  4:12                         ` Lynn Winebarger
2022-07-31 12:53                       ` Lynn Winebarger
2022-07-31 13:05                         ` Eli Zaretskii
2022-07-31 20:29                           ` Lynn Winebarger
2022-08-01  1:05                             ` Po Lu
2022-08-01 11:07                             ` Eli Zaretskii
2022-07-31  8:03                   ` Stefan Monnier
2022-07-31 12:43                     ` Lynn Winebarger
2022-07-31 21:32                       ` Stefan Monnier
2022-08-02 16:55                         ` Lynn Winebarger
2022-07-31 11:57               ` Lynn Winebarger
2022-07-31  0:52       ` Po Lu
2022-07-31  7:52     ` Stefan Monnier

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=831qu25z5x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=owinebar@gmail.com \
    /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).