From: Jean Louis <bugs@gnu.support>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Daniel Martín" <mardani29@yahoo.es>, emacs-devel@gnu.org
Subject: Re: A feature to go to last edit locations
Date: Mon, 13 Feb 2023 22:28:04 +0300 [thread overview]
Message-ID: <Y+qPRH69fo9s+rLo@protected.localdomain> (raw)
In-Reply-To: <f32abd98-3556-01e3-eac3-0c7df6bb9875@yandex.ru>
* Dmitry Gutov <dgutov@yandex.ru> [2023-02-12 21:53]:
> On 12/02/2023 20:50, Daniel Martín wrote:
> > Another question is how to track the edit locations efficiently. A
> > naive implementation would be to add a function to
> > after-change-functions if the xref setting is enabled.
>
> Sure, as one option. Except you'd have to differentiate user-made changes to
> the buffer and ones created by more complex commands, or timers, or
> auto-revert-mode...
One could do following:
- remember paragraph at point
- split it as words
- record those words
- jump to point
- search in buffer upwards and downwards for some regex like word.*word.*word.*
Maybe that think process could help in locating the exact point.
Or point could remember also the few words or line, and search for it
straight, up or down.
If it does not exist, point should destroy itself by asking user for it.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-02-13 19:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1fsbakchr.fsf.ref@yahoo.es>
2023-02-12 17:41 ` A feature to go to last edit locations Daniel Martín
2023-02-12 17:52 ` Eli Zaretskii
2023-02-12 18:59 ` Daniel Martín
2023-02-12 19:26 ` Eli Zaretskii
2023-02-12 19:42 ` andrés ramírez
2023-02-12 22:19 ` Daniel Martín
2023-02-12 23:54 ` Dr. Arne Babenhauserheide
2023-02-13 7:50 ` Juri Linkov
2023-02-12 21:40 ` [External] : " Drew Adams
2023-02-13 20:28 ` Jean Louis
2023-02-12 18:07 ` Dmitry Gutov
2023-02-12 18:50 ` Daniel Martín
2023-02-12 18:52 ` Dmitry Gutov
2023-02-12 19:23 ` Daniel Martín
2023-02-13 19:28 ` Jean Louis [this message]
2023-02-13 19:24 ` Jean Louis
2023-02-13 19:41 ` Dmitry Gutov
2023-02-13 20:22 ` Dr. Arne Babenhauserheide
2023-02-13 20:56 ` Jean Louis
2023-02-14 3:25 ` Eli Zaretskii
2023-02-14 4:36 ` [External] : " Drew Adams
2023-02-14 4:56 ` Drew Adams
2023-02-14 5:53 ` Jean Louis
2023-02-14 16:24 ` Drew Adams
2023-02-15 5:45 ` Jean Louis
2023-02-15 16:34 ` Drew Adams
2023-02-14 20:08 ` Dmitry Gutov
2023-02-13 19:48 ` [External] : " Drew Adams
2023-02-13 20:28 ` Dr. Arne Babenhauserheide
2023-02-13 21:17 ` Drew Adams
2023-02-13 21:21 ` Jean Louis
2023-02-13 21:14 ` Jean Louis
2023-02-14 5:21 ` Drew Adams
2023-02-13 19:49 ` Michael Welsh Duggan
2023-02-13 21:35 ` Jean Louis
2023-02-13 23:14 ` Konstantin Kharlamov
2023-02-14 0:00 ` Ergus
2023-02-14 6:29 ` Dr. Arne Babenhauserheide
2023-02-15 0:00 ` Karthik Chikmagalur
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=Y+qPRH69fo9s+rLo@protected.localdomain \
--to=bugs@gnu.support \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
/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).