From: Ypo <ypuntot@gmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: I can't set dabbrev to respect the writen case
Date: Sun, 15 May 2022 12:40:49 +0200 [thread overview]
Message-ID: <e6d75820-f3ab-df87-86af-f880d66f5a41@gmail.com> (raw)
In-Reply-To: <87v8u721ax.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Thanks, Juan Manuel.
These are my variables, it keeps changing what I have already written:
'(case-replace nil)
'(dabbrev-case-distinction t)
'(dabbrev-case-fold-search t)
'(dabbrev-case-replace t)
'(dabbrev-upcase-means-case-search nil)
Best regards,
Ypo
El 15/05/2022 a las 0:32, Juan Manuel Macías escribió:
> Ypo writes:
>
>> Hi
>>
>> 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,
>>
>> Ypo
>>
> Take a look at these variables. I have them configured as non-nil:
>
> (setq dabbrev-case-replace t)
>
> (setq dabbrev-case-fold-search t)
>
> Best regards,
>
> Juan Manuel
[-- Attachment #2: Type: text/html, Size: 1623 bytes --]
next prev parent reply other threads:[~2022-05-15 10:41 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 [this message]
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
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
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6d75820-f3ab-df87-86af-f880d66f5a41@gmail.com \
--to=ypuntot@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/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/org-mode.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).