From: Samuel Wales <firstname.lastname@example.org>
To: Ypo <email@example.com>
Cc: Org-mode <firstname.lastname@example.org>
Subject: Re: I can't set dabbrev to respect the writen case
Date: Mon, 16 May 2022 16:43:00 -0700 [thread overview]
Message-ID: <CAJcAo8vG_jok-cPHTmEcVoUa7tdwQ-FphWKTRZRPVGGdPC-K1g@mail.gmail.com> (raw)
did you confirm that fancy-dabbrev is not setting a dabbrev setting?
On 5/16/22, Samuel Wales <email@example.com> wrote:
> by default hippie-expand cycles. to cycle backward you can undo. idk
> if it or dabbrev has a menu.
> idk if this is useful but there is at least one menu package and many
> completion packages at seemingly varying levels of interoperability.
> some things have menus built in. there is some degree of modularity
> in some packages, especially a set of minibuffer completion packages,
> which is not waht you are looking for. i am confused by the many
> options. so what i would start with is as an ignoramus [that's me] is
> trying to find an overview of what's out there, dabbrev settings or a
> hook for a menu, he settings, whether anything with a menu incluing a
> menu package is intended to fit modularly into dabbrev, whether
> dabbrev or he fit into some framework [company?] that has or can use a
> menu. possibly you already tried those things but in cas nobod
> On 5/16/22, Ypo <firstname.lastname@example.org> wrote:
>> Thanks, Samuel
>> I've uninstalled fancy-dabbrev, and it seems to work when I complete
>> using M-/. But, now I don't have candidates to choose the completion.
>> Any advice with this?
>> Best regards,
>> El 16/05/2022 a las 0:15, Samuel Wales escribió:
>>> i do not use fancy-dabbrev, but i use dabbrev in hippie-expand. it
>>> seems to do as you want.
>>> it should be possible to run hippie-expand with just dabbrev. it
>>> might not be exactly the same because he might have its own version of
>>> dabbrev. which might be what you want in this case.
>>> note that you have control over where dabbrev gets its data. idk if
>>> that is a feature of vanilla dabbrev.
>>> i do not use any dabbrev settings or any he settings except the main
>>> one for he. it is set to
>>> ;;do i want this first? am i supposed to use another thing to
>>> ;;complete from that point?
>>> On 5/14/22, Ypo<email@example.com> wrote:
>>>> I find dabbrev and fancy-dabbrev very useful to typing fast. But there
>>>> is a problem I am not able to solve: When I apply an expansion while
>>>> writing, the case is always that of the expansion, I can't make it to
>>>> respect what I have written. An example:
>>>> — (Typing) "Hel
>>>> — (Offered expansion) "hello"
>>>> — (What I get when accepting the expansion) "hello"
>>>> — (What I wanted) "Hello"
>>>> Best regards,
> The Kafka Pandemic
> A blog about science, health, human rights, and misopathy:
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
next prev parent reply other threads:[~2022-05-16 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 19:58 I can't set dabbrev to respect the writen case Ypo
2022-05-14 22:32 ` Juan Manuel Macías
2022-05-15 10:40 ` Ypo
2022-05-15 13:58 ` Juan Manuel Macías
2022-05-15 22:15 ` Samuel Wales
2022-05-16 17:25 ` Ypo
2022-05-16 23:41 ` Samuel Wales
2022-05-16 23:43 ` Samuel Wales [this message]
2022-05-17 6:11 ` Ypo
2022-05-17 0:53 ` Tim Cross
2022-05-17 6:16 ` Ypo
2022-05-17 3:16 ` acdw
2022-05-17 3:52 ` Samuel Wales
2022-05-17 16:59 Ypo
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).