From: C K Kashyap <ckkashyap@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: dabbrev-expand ignores case sometimes
Date: Fri, 20 Jul 2012 10:36:09 +0530 [thread overview]
Message-ID: <CAGdT1gq4qYHe0cVxJ-2SngVUk2QdPr83uuup3ofinX-Xwhjn-A@mail.gmail.com> (raw)
In-Reply-To: <81394nzqnz.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
hmmm I am pretty sure its not M-I M-i or M-c . It's only M-/ and it simply
expands in an unexplainable manner.
Regards,
Kashyap
On Thu, Jul 19, 2012 at 9:31 PM, Jambunathan K <kjambunathan@gmail.com>wrote:
>
> Can you be more specific. What is the guarantee that you haven't typed
> M-l, M-u or M-c?
>
> > I have not customized dabrrev ... I believe I run into this
> > accidentally when I type in some control/alt combinations
> > inadvertently.
> >
> > Regards,
> > Kashyap
> >
> > On Thu, Jul 19, 2012 at 7:34 PM, Jambunathan K <
> > kjambunathan@gmail.com> wrote:
> >
> > C K Kashyap <ckkashyap@gmail.com> writes:
> >
> > > Hi,
> > >
> > > I noticed that at times when I do a M-/ and try to complete a
> > word
> > > that already exists in the buffer (I assume, this is what I
> > need to
> > > do if I need to do what I did using C-p or C-n on vi), the word
> > > completion happens but with weird casing. Sometime all caps
> > etc. I
> > > wonder if there is some setting I need to do when I get into
> > this
> > > situation.
> >
> > Have you customized dabrrev?
> >
> > See (info "(emacs) Dabbrev Customization")
> >
> >
> > >
> > > Regards,
> > > Kashyap
> > >
> > >
> >
> > --
>
[-- Attachment #2: Type: text/html, Size: 1999 bytes --]
next prev parent reply other threads:[~2012-07-20 5:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 13:09 dabbrev-expand ignores case sometimes C K Kashyap
2012-07-19 14:04 ` Jambunathan K
2012-07-19 15:03 ` C K Kashyap
2012-07-19 16:01 ` Jambunathan K
2012-07-20 5:06 ` C K Kashyap [this message]
2012-07-26 21:03 ` Ludwig, Mark
2012-08-05 19:43 ` Suvayu Ali
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=CAGdT1gq4qYHe0cVxJ-2SngVUk2QdPr83uuup3ofinX-Xwhjn-A@mail.gmail.com \
--to=ckkashyap@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=kjambunathan@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.
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).