From: "João Távora" <joaotavora@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Indentation of def*
Date: Wed, 20 Oct 2021 10:32:51 +0100 [thread overview]
Message-ID: <CALDnm52_75muw0yoK4HE-bRUCL7xRNP2wSp8GefgYr8zYspBXA@mail.gmail.com> (raw)
In-Reply-To: <87ee8gnlar.fsf@gnus.org>
On Wed, Oct 20, 2021 at 9:38 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> João Távora <joaotavora@gmail.com> writes:
>
> > Right. And your example is a _function_. Why don't you _at least_ keep
> > the heuristic for macros? Isn't that a worthy compromise, a "no-worse"
> > situation? It would fix your default-boundp example and, if Richard's
> > example deffoober is a macro (I'd say there's a good chance it is,
> > statistically speaking) then the calls to that macro would also be
> > indented correctly.
> > What am I missing?
> We've been over this. There's both functions and macros that want to be
> indented like a defun, and there both functions a macros that don't want
> to be, and sometimes they're called something that starts with def* and
> sometimes they don't.
Right, I know. I was referring to the example you gave. I've
also asked you for the listings that you've supposedly collected
on those things so we can make a better informed decision.
But, regardless, is it not so that there are various grades of
change here?
a - do nothing
b - keep heuristic but only for macros, delete for everything else.
c - delete heuristic entirely
From your perspective, isn't 'b' better than 'a'? Yes I get that, for you,
'c' > 'b' and that's why you did it.
But I think there are at least some situations where 'b' is preferrable.
So I'd like to have 'b' please. A compromise. We could add those
debug specs to the def _functions_ like your example. Whoever
these functions are and however many there are. Again, it'd be
great to have the data. Some data.
Thanks,
João
next prev parent reply other threads:[~2021-10-20 9:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 23:13 Indentation of def* Lars Ingebrigtsen
2021-10-14 4:22 ` Stefan Monnier
2021-10-14 11:07 ` Po Lu
2021-10-14 11:14 ` Lars Ingebrigtsen
2021-10-14 11:23 ` Lars Ingebrigtsen
2021-10-14 12:05 ` Po Lu
2021-10-14 12:09 ` Lars Ingebrigtsen
2021-10-14 12:22 ` Po Lu
2021-10-14 12:49 ` João Távora
2021-10-14 13:40 ` Lars Ingebrigtsen
2021-10-14 21:41 ` João Távora
2021-10-15 9:57 ` Lars Ingebrigtsen
2021-10-15 10:14 ` João Távora
2021-10-14 13:25 ` Stefan Kangas
2021-10-14 13:30 ` Po Lu
2021-10-14 19:06 ` Stefan Kangas
2021-10-14 23:42 ` Po Lu
2021-10-15 0:50 ` Stefan Kangas
2021-10-15 5:21 ` Po Lu
2021-10-15 6:50 ` Eli Zaretskii
2021-10-15 8:35 ` Stefan Kangas
2021-10-15 10:42 ` Eli Zaretskii
2021-10-15 13:07 ` Stefan Kangas
2021-10-15 13:30 ` Eli Zaretskii
2021-10-15 13:48 ` Stefan Kangas
2021-10-15 13:17 ` Stefan Monnier
2021-10-15 12:42 ` Lars Ingebrigtsen
2021-10-15 12:43 ` Lars Ingebrigtsen
2021-10-14 18:35 ` Stefan Monnier
2021-10-18 8:02 ` Lars Ingebrigtsen
2021-10-20 6:47 ` Richard Stallman
2021-10-20 7:52 ` Lars Ingebrigtsen
2021-10-20 8:19 ` João Távora
2021-10-20 8:38 ` Lars Ingebrigtsen
2021-10-20 9:32 ` João Távora [this message]
2021-10-20 9:36 ` Lars Ingebrigtsen
2021-10-20 16:10 ` João Távora
2021-10-23 23:26 ` Richard Stallman
2021-10-24 13:22 ` Lars Ingebrigtsen
2021-10-24 14:27 ` Stefan Kangas
2021-10-24 15:19 ` João Távora
2021-10-24 16:23 ` Stefan Monnier
2021-10-24 16:55 ` Lars Ingebrigtsen
2021-10-24 18:36 ` João Távora
2021-10-27 14:37 ` Richard Stallman
2021-10-27 14:36 ` Richard Stallman
2021-10-27 14:40 ` Lars Ingebrigtsen
2021-10-30 6:49 ` 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=CALDnm52_75muw0yoK4HE-bRUCL7xRNP2wSp8GefgYr8zYspBXA@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@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).