emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ypo <ypuntot@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: I can't set dabbrev to respect the writen case
Date: Mon, 16 May 2022 19:25:16 +0200	[thread overview]
Message-ID: <ebf55b66-1625-03f0-4b60-56559ae9f5d2@gmail.com> (raw)
In-Reply-To: <CAJcAo8sAq6xjQGqxQG_1gYvVRFc9_jEdG6yE=A7g7qjCVzeTWA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]

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,
Ypo

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
>
>        '(try-expand-dabbrev-visible
>          try-expand-dabbrev
>          try-expand-dabbrev-all-buffers
>          try-expand-dabbrev-from-kill
>
>          try-complete-lisp-symbol
>          ;;do i want this first?  am i supposed to use another thing to
>          ;;complete from that point?
>          ;;try-complete-lisp-symbol-partially
>
>          ;;try-expand-whole-kill
>          try-complete-file-name-partially
>          try-complete-file-name
>          hoka-try-complete-with-calc-result)
>
>
> On 5/14/22, Ypo<ypuntot@gmail.com>  wrote:
>> 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
>>
>

[-- Attachment #2: Type: text/html, Size: 2491 bytes --]

  reply	other threads:[~2022-05-16 17:26 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=ebf55b66-1625-03f0-4b60-56559ae9f5d2@gmail.com \
    --to=ypuntot@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    /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).