From: Eli Zaretskii <eliz@gnu.org>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: spacibba@aol.com, emacs-devel@gnu.org
Subject: Re: highlight-indent-guides in display engine
Date: Sun, 14 Jul 2019 08:37:31 +0300 [thread overview]
Message-ID: <83ef2tyy5g.fsf@gnu.org> (raw)
In-Reply-To: <87o91xfwfo.fsf@fastmail.fm> (message from Joost Kremers on Sat, 13 Jul 2019 23:37:15 +0200)
> From: Joost Kremers <joostkremers@fastmail.fm>
> Date: Sat, 13 Jul 2019 23:37:15 +0200
> Cc: spacibba@aol.com
>
> > Then I guess you are one of those for whom the built-in feature
> > will not be good enough, and you will keep using some 3rd party
> > package.
>
> Just my opinion, but from a user's perspective it might seem
> rather strange that a feature that Emacs supports out of the box
> does *not* work with Lisp. With any other editor I might think "oh
> well", but Emacs *is* Lisp.
So you are saying that we should not provide this as a built-in
feature unless we also support dynamic indentation that doesn't heed
to tab stops and tab-width?
next prev parent reply other threads:[~2019-07-14 5:37 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
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 [this message]
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=83ef2tyy5g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joostkremers@fastmail.fm \
--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).