From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Resources for an old newbie ?
Date: Mon, 05 Jun 2023 04:59:37 +0200 [thread overview]
Message-ID: <873536sjfq.fsf@web.de> (raw)
In-Reply-To: SJ0PR03MB545539EEEEB5682E34C517FCA24DA@SJ0PR03MB5455.namprd03.prod.outlook.com
David Masterson <dsmasterson@gmail.com> writes:
> I think it was something about docstring width.
>
> But I've spent too much time on this.
Don't want to suggest which Emacs version to use - but for your private
stuff, you can just ignore those warnings about docstrings (or just turn
them off, locally). You have no disadvantages to fear when using that
code with the new Emacs version. The compiler warnings just have been
improved, there are more checks. If something really doesn't work, then
there is a high chance that the same code will fail in older Emacs
versions, too.
Michael.
next prev parent reply other threads:[~2023-06-05 2:59 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 0:44 Resources for an old newbie ? Frederick Bartlett
2023-05-22 0:50 ` Eduardo Ochs
2023-05-22 1:30 ` Michael Heerdegen
2023-05-22 1:39 ` Michael Heerdegen
2023-05-22 6:33 ` Basile Starynkevitch
2023-05-23 0:11 ` Michael Heerdegen
2023-05-23 5:31 ` Emanuel Berg
2023-05-23 20:19 ` Philip Kaludercic
2023-05-25 0:55 ` Emanuel Berg
2023-05-23 23:09 ` Michael Heerdegen
2023-05-25 1:13 ` Emanuel Berg
2023-05-26 3:28 ` Michael Heerdegen
2023-05-27 5:41 ` Emanuel Berg
2023-05-28 1:50 ` Michael Heerdegen
2023-05-28 21:23 ` Emanuel Berg
2023-05-24 4:25 ` tomas
2023-05-25 1:25 ` Emanuel Berg
2023-05-25 4:01 ` tomas
2023-05-26 1:26 ` David Masterson
2023-05-26 3:36 ` Michael Heerdegen
2023-05-26 4:13 ` Robby Zambito
2023-05-27 4:09 ` David Masterson
2023-05-27 5:29 ` Emanuel Berg
2023-05-29 22:13 ` David Masterson
2023-05-27 5:48 ` Emanuel Berg
2023-05-29 22:14 ` David Masterson
2023-05-27 17:48 ` Robby Zambito
2023-05-29 22:23 ` David Masterson
2023-05-28 2:12 ` Michael Heerdegen
2023-05-28 21:26 ` Emanuel Berg
2023-05-29 22:21 ` David Masterson
2023-05-29 22:52 ` Michael Heerdegen
2023-05-30 2:18 ` Emanuel Berg
2023-06-03 21:40 ` David Masterson
2023-05-30 23:24 ` Emanuel Berg
2023-05-31 3:12 ` Platon Pronko
2023-05-31 3:20 ` Emanuel Berg
2023-05-31 22:07 ` Michael Heerdegen
2023-06-03 21:45 ` David Masterson
2023-06-03 22:03 ` Michael Heerdegen
2023-06-03 22:39 ` David Masterson
2023-06-03 23:19 ` Michael Heerdegen
2023-06-04 1:00 ` David Masterson
2023-06-04 1:31 ` Emanuel Berg
2023-06-04 2:15 ` Michael Heerdegen
2023-06-04 5:23 ` David Masterson
2023-06-04 2:21 ` Emanuel Berg
2023-06-04 21:05 ` David Masterson
2023-06-06 16:45 ` Emanuel Berg
2023-06-04 3:02 ` Emanuel Berg
2023-06-04 21:01 ` David Masterson
2023-06-04 5:25 ` Eli Zaretskii
2023-06-04 7:08 ` Basile Starynkevitch
2023-06-04 20:35 ` David Masterson
2023-06-04 7:26 ` David Masterson
2023-06-04 7:37 ` Eli Zaretskii
2023-06-04 10:45 ` Emanuel Berg
2023-06-04 20:07 ` David Masterson
2023-06-04 22:12 ` Michael Heerdegen
2023-06-04 22:36 ` David Masterson
2023-06-05 20:34 ` Emanuel Berg
2023-06-05 20:35 ` Emanuel Berg
2023-06-04 10:39 ` Emanuel Berg
2023-06-04 20:23 ` David Masterson
2023-06-05 0:29 ` Michael Heerdegen
2023-06-05 2:22 ` David Masterson
2023-06-05 2:59 ` Michael Heerdegen [this message]
2023-06-06 1:19 ` Emanuel Berg
2023-06-06 16:35 ` Emanuel Berg
2023-06-11 3:14 ` Michael Heerdegen
2023-06-11 4:48 ` David Masterson
2023-06-11 6:02 ` Emanuel Berg
2023-06-11 23:33 ` Michael Heerdegen
2023-06-11 23:41 ` Emanuel Berg
2023-06-16 2:22 ` Michael Heerdegen
2023-06-16 2:27 ` Michael Heerdegen
2023-06-11 5:54 ` Emanuel Berg
2023-06-11 23:42 ` Michael Heerdegen
2023-06-11 23:56 ` Emanuel Berg
2023-06-05 20:41 ` Emanuel Berg
2023-06-03 21:33 ` David Masterson
2023-05-26 4:28 ` tomas
2023-05-26 11:34 ` Robert Pluim
2023-05-26 12:06 ` tomas
2023-05-26 14:11 ` Robert Pluim
2023-05-26 21:40 ` Emanuel Berg
2023-06-08 8:39 ` Emanuel Berg
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=873536sjfq.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).