From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lynn Winebarger Newsgroups: gmane.emacs.devel Subject: Re: Docstring hack Date: Sun, 31 Jul 2022 07:57:59 -0400 Message-ID: References: <83bkt6687a.fsf@gnu.org> <871qu2lo29.fsf@yahoo.com> <837d3u63ez.fsf@gnu.org> <834jyy61w6.fsf@gnu.org> <831qu25z5x.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000fbdfa505e518984c" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37624"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 31 13:58:51 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oI7at-0009cu-QB for ged-emacs-devel@m.gmane-mx.org; Sun, 31 Jul 2022 13:58:51 +0200 Original-Received: from localhost ([::1]:60664 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oI7as-0004JE-J0 for ged-emacs-devel@m.gmane-mx.org; Sun, 31 Jul 2022 07:58:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58146) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oI7aK-0003de-Dj for emacs-devel@gnu.org; Sun, 31 Jul 2022 07:58:16 -0400 Original-Received: from mail-pj1-x102d.google.com ([2607:f8b0:4864:20::102d]:33762) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oI7aI-00035l-Ok; Sun, 31 Jul 2022 07:58:16 -0400 Original-Received: by mail-pj1-x102d.google.com with SMTP id f11-20020a17090a4a8b00b001f2f7e32d03so10115886pjh.0; Sun, 31 Jul 2022 04:58:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qej2mM4MIPeNcyf+eJlkAh8dJeE16WQg0y/OFSX3W3s=; b=JNw26v2UAxIZn5f7WSiuS1hfDjuhBa54reEnqDH+z+Iv+IKeAJXb2isYWb+eehZtjT h1Kqs8aohFGkFeX6TqNG+w+CRDVgHl7kmA6Ez0B+OKlP7i7x5v0RJcNUzBQWvGxXIrJl LFezjtwjRyqM1iegqw0DMYUGxUuE3M/Eu2rmvH/+jHSgJf3WP8mnlxIW+wOPBMQMSJiB EaumtsRTGT1a5f1yL2ssGCMKHi1HOMhyzJAgUc7tTTrg1tPRxbMfr0p84dxs9oHUiL6q KCn0NUjkOrpWA4K/Q5jgO9Dao2FJHI1eIIX3daCHy5zwlStmtHq2CqzcTbBzCqk+q91g KFuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qej2mM4MIPeNcyf+eJlkAh8dJeE16WQg0y/OFSX3W3s=; b=apQkaHNFqFsLi0rS2V/BZa15jaVdDqzwdzrr8XfbTm5p2kHAX1GQB21I05s3+KnwP8 wFnP5L1JSs/qi9U7Ywu546z5miqs1NXF9D+cUd5cuVdRC13fZCszh80Xycgr1NCsKCq4 r/kotz4KJgGFuVQYRGyBNPhqiO/PVQMhsNG5Ucu45YbKusu/htd6tC09+DhH74yOCtVh QM9gNXxjb4rJDJMK/lfmPF+IwGdt8OFiv+pYy0rElTkplNwwXm2jFYlf3avJkDQzseN3 WobG/W8do0X3etQnUJJDDJwZgHbGncBb8VrAA6r7L1apJiCTsyxrYTn0WcObmFR0jaX3 EkBw== X-Gm-Message-State: ACgBeo0YpVFBMUWCrLPjHAg4VsbCjlMy9g2GAfwUoPjVYe34JITXv12w NJxslVZ6Q3y0IaW5pP/7S3DI47UnGeWGpLNlTH9SdyEd X-Google-Smtp-Source: AA6agR51E5dER2pSWdSCla31cX57bFQ84LTAqaO+UU3ZxBM7SJiR9liKyz0L5a6yP9BtoEFGcOXPm3NR6pjWiYvs61M= X-Received: by 2002:a17:90a:2948:b0:1f3:1b42:a810 with SMTP id x8-20020a17090a294800b001f31b42a810mr14127601pjf.203.1659268692171; Sun, 31 Jul 2022 04:58:12 -0700 (PDT) In-Reply-To: <831qu25z5x.fsf@gnu.org> Received-SPF: pass client-ip=2607:f8b0:4864:20::102d; envelope-from=owinebar@gmail.com; helo=mail-pj1-x102d.google.com X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:292913 Archived-At: --000000000000fbdfa505e518984c Content-Type: text/plain; charset="UTF-8" On Sat, Jul 30, 2022, 12:43 PM Eli Zaretskii wrote: > > From: Lynn Winebarger > > Date: Sat, 30 Jul 2022 12:32:27 -0400 > > Cc: luangruo@yahoo.com, emacs-devel > > > > 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? > I'm sorry, I misread the exchange with Po and the response to my other question as being dismissive, and I see I was incorrect. I just spent way too many hours stepping through code looking for some weird memory corruption issue before discovering the location of the hack in the source. I had actually looked for it before in lread.c, but for some reason did not find it, since I had seen references to this kind of issue in the documentation. Thanks for the attention to the matter - I believe others have answered these questions, I'll respond to those. Lynn --000000000000fbdfa505e518984c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jul 30, 2022, 12:43 PM Eli Zaretskii <eliz@gnu.org>= ; wrote:
> From: Lynn Winebarger= <owinebar@gmail.com>
> Date: Sat, 30 Jul 2022 12:32:27 -0400
> Cc: luangruo@yahoo.com, emacs-devel <ema= cs-devel@gnu.org>
>
>=C2=A0 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.=C2=A0 Do I really deserve a cold
shower for asking such questions?

I'm sorry, I misread the exchange with= Po and the response to my other question as being dismissive, and I see I = was incorrect.
I just spent way too many hours stepp= ing through code looking for some weird memory corruption issue before disc= overing the location of the hack in the source.=C2=A0 I had actually looked= for it before in lread.c, but for some reason did not find it, since I had= seen references to this kind of issue in the documentation.=C2=A0
Thanks for the attention to the matter - I believe others ha= ve answered these questions, I'll respond to those.

Lynn

--000000000000fbdfa505e518984c--