From: Drew Adams <drew.adams@oracle.com>
To: Ergus <spacibba@aol.com>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: highlight-indent-guides in display engine
Date: Fri, 12 Jul 2019 12:35:43 -0700 (PDT) [thread overview]
Message-ID: <27150cdb-9524-49e7-93f8-d20d3e9d41a7@default> (raw)
In-Reply-To: <20190712185100.omyyovxh5hqzpk5z@Ergus>
> But also there is not any answer/suggestion about what to do with the
> irregular indentation in Lisp...
Since you've asked that a couple times now,
here's my take on it.
It's not at all _needed_ for Lisp. And personally
I wouldn't find it useful for Lisp.
Lisp has simple syntax - it's sufficient to
balance parens. Automatic and on-demand
indentation work off of that syntax.
And most Lisp code does not have many-line
stretches with a large indentation, so you don't
often need to worry about line-of-sight alignment.
And checking column number is easy enough for any
exceptional cases.
Many other languages are different. For them I
can see how it could be useful for some users.
Just one opinion.
next prev parent reply other threads:[~2019-07-12 19:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 21:17 highlight-indent-guides in display engine Ergus
2019-07-07 15:04 ` Eli Zaretskii
2019-07-11 19:06 ` Ergus
2019-07-11 19:15 ` Eli Zaretskii
2019-07-12 0:21 ` Ergus
2019-07-12 6:57 ` Eli Zaretskii
2019-07-12 9:58 ` Ergus
2019-07-12 10:36 ` Ergus
2019-07-12 13:45 ` Eli Zaretskii
2019-07-12 18:51 ` Ergus
2019-07-12 19:35 ` Drew Adams [this message]
2019-07-13 6:59 ` Eli Zaretskii
2019-07-13 8:32 ` Joost Kremers
2019-07-13 8:38 ` Eli Zaretskii
2019-07-13 21:37 ` Joost Kremers
2019-07-14 5:37 ` Eli Zaretskii
2019-07-15 5:44 ` Joost Kremers
2019-07-14 12:56 ` Ergus
2019-07-15 12:58 ` Stefan Monnier
2019-07-15 14:11 ` Ergus
2019-07-15 14:49 ` Stefan Monnier
2019-07-15 17:10 ` Ergus
2019-07-15 18:43 ` Stefan Monnier
2019-07-16 8:06 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-07-07 17:50 Keith David Bershatsky
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=27150cdb-9524-49e7-93f8-d20d3e9d41a7@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=spacibba@aol.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).