From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: find-file-dwim.el
Date: Tue, 23 Jul 2024 15:08:48 +0200 [thread overview]
Message-ID: <87bk2oqmqn.fsf@dataswamp.org> (raw)
In-Reply-To: 87frs0jtok.fsf@posteo.net
Philip Kaludercic wrote:
> That is what confused me. Usually people don't share
> prototypes this early with the mailing list.
It is amazing to behold: not everyone does everything the
same way.
> But of course it is also up to you where you'd like to have
> this kind of a feature added, as soon as it is
> mature enough.
It must also be tested to see if it really is an improvement
before any of that can be contemplated.
> But as mentioned in my comments, you should clarify what the
> "DWIM" aspect of your script is. Find-file already has some
> DWIM-ish stuff going on with the "future history" (M-n), so
> I am guessing your plan is to do something different?
I have several ideas and they are not opposed to each other so
maybe I'll do all of them. The most simplest idea is based on
the COLLECTION which will be updated on the fly and limited to
a smaller scope.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2024-07-23 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 22:10 find-file-dwim.el Emanuel Berg
2024-07-22 3:33 ` find-file-dwim.el Emanuel Berg
2024-07-22 14:02 ` find-file-dwim.el Philip Kaludercic
2024-07-22 15:40 ` find-file-dwim.el Emanuel Berg
2024-07-23 0:47 ` find-file-dwim.el Emanuel Berg
2024-07-23 6:41 ` find-file-dwim.el Philip Kaludercic
[not found] ` <87jzhcqw4a.fsf@dataswamp.org>
2024-07-23 10:20 ` find-file-dwim.el Philip Kaludercic
2024-07-23 13:08 ` Emanuel Berg [this message]
2024-07-23 13:01 ` find-file-dwim.el Emanuel Berg
2024-07-23 7:06 ` find-file-dwim.el Michael Albinus
2024-07-25 9:24 ` find-file-dwim.el Emanuel Berg
2024-07-22 5:32 ` find-file-dwim.el Emanuel Berg
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=87bk2oqmqn.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@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 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.