From: Drew Adams <drew.adams@oracle.com>
To: Yuri Khan <yuri.v.khan@gmail.com>, Rusi <rustompmody@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: RE: emacs <--> file-browser as coroutines
Date: Mon, 27 Jun 2016 06:59:34 -0700 (PDT) [thread overview]
Message-ID: <1a7a1faf-9183-494e-95dc-3d11d3788eed@default> (raw)
In-Reply-To: <CAP_d_8WXvHhm0YmNF84J9p7iyPNMFMSOTBO26wrOgm7NpBbicg@mail.gmail.com>
> Also, it might be a good idea to start Emacs with a Dired open at the
> user’s home or Documents directory. That’s one more workflow for
> opening files in Emacs; one that I personally use the most.
Absolutely! That's what I've always done. It just makes sense, to me.
prev parent reply other threads:[~2016-06-27 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 7:09 emacs <--> file-browser as coroutines Rustom Mody
2016-06-27 8:18 ` Yuri Khan
[not found] ` <mailman.161.1467015515.26859.help-gnu-emacs@gnu.org>
2016-06-27 9:14 ` Rusi
2016-06-27 10:09 ` Yuri Khan
2016-06-27 13:59 ` Drew Adams [this message]
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=1a7a1faf-9183-494e-95dc-3d11d3788eed@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rustompmody@gmail.com \
--cc=yuri.v.khan@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).