From: Tom Horsley <tomhorsley@comcast.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Consolidating Widely used Powerful emacs "features"
Date: Sat, 16 Feb 2008 19:08:16 -0600 [thread overview]
Message-ID: <nsCdnX5dTPWdFCranZ2dnUVZ_gKdnZ2d@comcast.com> (raw)
In-Reply-To: mailman.7488.1203182995.18990.help-gnu-emacs@gnu.org
On Sat, 16 Feb 2008 09:29:45 -0800, Sanjeev Kumar.S wrote:
> <Please delete this line and add more>
dabbrev - can't live without it (but I sure wish there was
a combination of settings I could use to make it search
in a case-insensitive fashion, but return possible matches
in a case sensitive fashion so I wouldn't keep getting
screwed up in all those stoopid X programs that use
littleName and LittleName in the same file for different
things :-).
next prev parent reply other threads:[~2008-02-17 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7488.1203182995.18990.help-gnu-emacs@gnu.org>
2008-02-16 17:48 ` Consolidating Widely used Powerful emacs "features" David Kastrup
2008-02-17 1:08 ` Tom Horsley [this message]
2008-02-16 16:16 Latest version of emacs for Cygwin Oleksandr Gavenko
2008-02-16 17:29 ` Consolidating Widely used Powerful emacs "features" Sanjeev Kumar.S
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=nsCdnX5dTPWdFCranZ2dnUVZ_gKdnZ2d@comcast.com \
--to=tomhorsley@comcast.net \
--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).