From: "Samuel Wales" <samologist@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: ideas for customize
Date: Sat, 3 Jan 2009 17:12:27 -0700 [thread overview]
Message-ID: <20524da70901031612x2b18c160oe9391f7060afe2a8@mail.gmail.com> (raw)
In-Reply-To: <002b01c96dff$88e3fa60$0200a8c0@us.oracle.com>
Hi Drew,
I have severe typing issues, so cannot develop it, but I will forward
it. Thanks.
BTW, are you the icicles person? I keep being tantalized yet
intimidated by it.
For what it's worth, what would convince me to try it again is if it
could be set to emulate ido (without that changing anything else).
Dunno if it's possible or if you're interested, but thought I would
let you know.
This would include emulating ido's use in org-mode for outline paths.
Cheers.
next prev parent reply other threads:[~2009-01-04 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 23:49 ideas for customize Samuel Wales
2009-01-04 0:01 ` Drew Adams
2009-01-04 0:12 ` Samuel Wales [this message]
2009-01-04 0:57 ` Drew Adams
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=20524da70901031612x2b18c160oe9391f7060afe2a8@mail.gmail.com \
--to=samologist@gmail.com \
--cc=drew.adams@oracle.com \
--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).