From: Dale Snell <ddsnell@frontier.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Moving from Ido to Icicles
Date: Sat, 1 Nov 2014 07:48:04 -0700 [thread overview]
Message-ID: <20141101074804.1fde2b3a@zothique> (raw)
In-Reply-To: <8761ez6x0n.fsf@wmi.amu.edu.pl>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
On Sat, 01 Nov 2014 11:22:16 +0100
Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
> There is one feature of Ido, however, which is very important for me.
> Is this possible in Icicles? (I should probably ask "how do I do it
> in Icicles?", though...) I mean persistent history of visited
> files. I seldom restart my Emacs, but sometimes I do, and I don't
> want to lose my history then. (On the other hand, instead of history
> per se, I could probably do with the set of all *.tex, *.org, *.el
> and maybe a few other files for now – and just in case I start to
> e.g. learn Python, I could just add one more extension to the list.
> What might be a better workflow?)
I can't speak for Icicles, I've never used it. Besides, that's Drew's
job. :-) However, you might want to look into "recentf", which is a
built-in package. It keeps a list of the <n> most recently opened
files. The value of <n> defaults to sixteen, as I recall, but it
can be changed. When you access the list (from the menu bar or from C-x
C-r) it presents you with that list. You can then select the file
you want to open. I've found it quite handy.
Anyway, I hope this helps.
--Dale
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-11-01 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 10:22 Moving from Ido to Icicles Marcin Borkowski
2014-11-01 14:48 ` Dale Snell [this message]
2014-11-01 21:07 ` Robert Thorpe
2014-11-01 23:35 ` Will O'Brien
2014-11-04 7:23 ` 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=20141101074804.1fde2b3a@zothique \
--to=ddsnell@frontier.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).