From: Samuel Wales <samologist@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: help-gnu-emacs@gnu.org
Subject: Re: crash-proof emacs use
Date: Wed, 14 Sep 2022 19:49:31 -0700 [thread overview]
Message-ID: <CAJcAo8tkHtc-N-Z3w5bYkRJznVhvL-By8PrtJjcf4nnrDRh_JA@mail.gmail.com> (raw)
In-Reply-To: <875yht6o9x.fsf@mbork.pl>
thanks!
i'd say stefan's example here is more or less the canonical/cynosure
one for non-crash-proof editing, but i am open to other
crash-proof-ness:
- kill, with the intent to yank elsewhere
- forget all about it
- save
knowing that i have to remmber and that i might forget or some other
thing is stressful and cognitively burdensome even if i do not forget.
computers shold be able to do some of that kind of organizing for me.
at least that is the idea.
editing some part of a sentence doesn't do this to me as much.
sending paragraphs elsewhere does.
or
perhaps it extends to complex org/elisp/bash editing or various types
of linking, perhaps ones where stuff has to be kept in sync or all
bases need covering. i think it might be related to the "keeping a
stack of state in one's head" kind of thing, including cases where it
is too inconvenient/bad for rsi to literally keep on top of one's org capture
stack. n.b. i always use only one window. but it also has to be
convenient and low rsi.
idk, lots of possibilities. kill, then hit an f key to say "this kill
has to be yanked someplace", maybe. idk.
p.s. i just thought of another example of crash-proof-ness. suppose
you decide that bef and aft are not sortable, and same with start and
end, and start and finish, so you decide to canonicalize on beg and
end. and for times, bt and et.
so you use query-replace-regexp, which has 2 problems here. one is
that you want it for multiple files, which wgrep can help with.
although it could perhaps treat all of its matches as if they were in
one file.
the other is the example. you want to replace all those with beg and
all those with end at the same time. you don't want to forget to do
the end part for any one of those start parts that you changed.
thus, as an example, a crash-proof query-replace-regexp would allow
multiple pairs of replacements. perhaps with different colors, one
per pair. but this is a less common need than crash-proof moving.
btw i am not on this list i think.
On 9/12/22, Marcin Borkowski <mbork@mbork.pl> wrote:
>
> On 2022-09-12, at 04:13, Samuel Wales <samologist@gmail.com> wrote:
>
>> suppose you want to move something from one place to another. in org,
>> you can often use org-refile. that is more or less an atomic
>> operation. but suppose that for whatever reason you cannot do that,
>> so you use traditional emacs.
>
>> [...]
>
> That is a _very_ interesting idea! I might be tempted to code something
> like this (assuming nobody did it earlier, which would not surprise me).
>
> That said, for a similar reason (it is easy to delete something in Org
> and not notice because of all the hiding), I developed a habit of
> committing my org-mode files to Git (almost) every day (at least 0.8
> times per day on average, to be more precise). That helps.
>
> Best,
>
> --
> Marcin Borkowski
> http://mbork.pl
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2022-09-15 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 2:13 crash-proof emacs use Samuel Wales
2022-09-12 3:26 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-12 6:08 ` Jean Louis
2022-09-12 6:32 ` Yuri Khan
2022-09-12 7:32 ` Marcin Borkowski
2022-09-15 2:49 ` Samuel Wales [this message]
2022-09-17 14:22 ` Marcin Borkowski
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=CAJcAo8tkHtc-N-Z3w5bYkRJznVhvL-By8PrtJjcf4nnrDRh_JA@mail.gmail.com \
--to=samologist@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/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.
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).