From: Ihor Radchenko <yantar92@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Vladimir Nikishkin <lockywolf@gmail.com>, emacs-devel@gnu.org
Subject: Re: Fwd: A TAB operation reform question.
Date: Wed, 12 Oct 2022 14:57:11 +0800 [thread overview]
Message-ID: <87a661sf5k.fsf@localhost> (raw)
In-Reply-To: <jwvh70av5vk.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> A `tab-dwim-function` var is a bit more delicate to configure than
> a `tab-dwim-functions` var, but I think neither of them would be usable
> via Custom anyway (because it's often overridden buffer-locally by
> major/minor modes).
>
> This said, a `tab-dwim-functions` would be a great improvement over
> what have, in any case.
What about going further and allowing customization for dwim commands?
I imagine something like (defun-dwim ...), which can later be extended
to act differently depending on major mode or any other condition. For
example, special modes will then need not rely upon the key binding
conventions, say for next/previous line (C-n/C-p). If the user can
simply re-bind next-line-dwim/previous-line-dwim and get all the major
modes obey the new binding without a need to do major-mode-specific
customizations.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2022-10-12 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 15:03 A TAB operation reform question Vladimir Nikishkin
2022-10-10 15:49 ` Christopher Dimech
2022-10-11 0:01 ` Emanuel Berg
2022-10-11 9:15 ` Thibaut Verron
2022-10-11 10:25 ` Emanuel Berg
2022-10-11 2:37 ` Fwd: " Vladimir Nikishkin
2022-10-11 6:15 ` Emanuel Berg
2022-10-11 12:54 ` Stefan Monnier
2022-10-11 12:59 ` Vladimir Nikishkin
2022-10-11 13:48 ` Stefan Monnier
2022-10-12 6:57 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a661sf5k.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lockywolf@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.