From: Ingo Lohmar <i.lohmar@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Heading/item insert commands
Date: Wed, 4 Oct 2017 13:27:44 +0200 [thread overview]
Message-ID: <CACfmNMXq6OfBQJB7JSb_wMY5L4rJ__amDrH4q47R0QMgc42oeQ@mail.gmail.com> (raw)
In-Reply-To: <871smjgq3l.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
Hi Nicolas,
I am not sure I understand: As I tried to make clear, I am *not* interested
in changing the UI for anybody but myself. I probably should have omitted
the "long-run" comment altogether.
What I am interested in is refactoring: add a layer of functions that
cleanly do what is now done in an ad-hoc way, eg, inside
of-insert-todo-heading, or which is not done at all.
Or are you talking about the parameters of such new functions?
On Oct 4, 2017 12:33 PM, "Nicolas Goaziou" <mail@nicolasgoaziou.fr> wrote:
Hello,
Ingo Lohmar <i.lohmar@gmail.com> writes:
> What I have in mind for starters:
>
> Add orthogonal internal functions that can handle *all* sensible
> combinations of requirements. Then rewrite existing commands in terms
> of these, but possibly adding new ones.
>
> I would not want to break any workflows, of course. But in the *long*
> run, we could rethink if the existing commands and their prefix-arg
> behavior are really what users want, or if we provide other ones by
> default.
>
> Does that sound reasonable, or are there any grave obstacles I did not
> consider, or any hard reasons why such changes could not be accepted?
I think, as a starter, we should discuss and agree on how the UI should
be. IMO, implementation follows, not the other way around.
WDYT?
Regards,
--
Nicolas Goaziou
[-- Attachment #2: Type: text/html, Size: 2059 bytes --]
next prev parent reply other threads:[~2017-10-04 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 18:52 Heading/item insert commands Ingo Lohmar
2017-10-04 10:33 ` Nicolas Goaziou
2017-10-04 11:27 ` Ingo Lohmar [this message]
2017-10-06 17:54 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACfmNMXq6OfBQJB7JSb_wMY5L4rJ__amDrH4q47R0QMgc42oeQ@mail.gmail.com \
--to=i.lohmar@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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/org-mode.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).