From: Samuel Wales <samologist@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: basic navigation
Date: Tue, 4 Jul 2023 21:17:15 -0700 [thread overview]
Message-ID: <CAJcAo8vv=fV-c28P31G5qUzsFs1v0mo3Qq0jEdoce+n0QQ+=UA@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8t++LCwW+EbS8_L0nyoszB1sqitZg61HaVCXQeWgYzHwg@mail.gmail.com>
there are a few issues here actually. first is that non-words get
gobbled up along with words. this is too much for my taste. i'd be
ok with each chunk of non-word syntax being kind of like a word, for
example.
the other thing i did not illustrate. going left means going to bow.
but going right means going to, not eow, but the space. similar with
paragraphs and so on.
suppose i am at bow.
this is ^a word.
and i want to kill-word that. i end up with 2 spaces. so sometimes i
do gyrations to kill the right thing. it's too much for me.
the adage that emacs is a superb os but it lacks a decent editor is,
for me, almost true, with these little [intentional, but not quite
working well for me] glitches. maybe a package?
On 7/4/23, Samuel Wales <samologist@gmail.com> wrote:
> ***** basic navigation and killing
> i am wondering if there are packages that can do this kind
> of thing better.
>
> this applies to any editing. here is an example. suppose i
> am on an org-mode heading, with point at ^.
>
> never mind the actual text. my goal is to transform it to
> this.
>
> *** ^gather and do physical
>
> so i do the first thing that comes to mind: c-backspace
> which runs backward-kill-word in my emacs 27.1.
>
> there are of course many other things i can do, instead,
> such as go to bol, use delete-char, etc., but i want to
> illustrate basic word killing with this example. what
> occurs is this, successively.
>
> *** --- /various to do/ and to ^gather and do physical
> *** --- /various to do/ and ^gather and do physical
> *** --- /various to do/ ^gather and do physical
> *** --- /various to ^gather and do physical
>
> i don't particularly mind the command's ignorance of org
> syntax here.
>
> *** --- /various ^gather and do physical
> *** --- /^gather and do physical
>
> and then once more to get rid of the --- syntax, which is a
> bit of an emacs editing disaster. what i wanted was to have
> it produce what i set out to do. maybe naive, but i wonder
> if there might be different killing/nav paradigms.
>
> i've been vexed by this since the 1980s with only sporadic
> attempts to see if i can improve on it. time to rely on
> others for some ideas and possible existing packages.
> please be gentle with me. am cognitively impaired.
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2023-07-05 4:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 3:55 basic navigation Samuel Wales
2023-07-05 4:16 ` Platon Pronko
2023-07-05 4:24 ` Samuel Wales
2023-07-05 4:33 ` Platon Pronko
2023-07-05 4:41 ` Samuel Wales
2023-07-05 4:17 ` Samuel Wales [this message]
2023-07-05 5:51 ` Emanuel Berg
2023-07-13 0:18 ` Samuel Wales
2023-07-13 0:34 ` 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
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='CAJcAo8vv=fV-c28P31G5qUzsFs1v0mo3Qq0jEdoce+n0QQ+=UA@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=help-gnu-emacs@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.
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).