From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Oleksandr Gavenko <gavenkoa@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Directories for Ezwinports
Date: Sat, 10 Jan 2015 21:08:56 +0000 [thread overview]
Message-ID: <87lhlaibrr.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <87h9vzahv6.fsf@gavenkoa.example.com> (message from Oleksandr Gavenko on Fri, 09 Jan 2015 21:12:13 +0200)
Thanks a lot, I did something very similar.
BR,
Robert Thorpe
Oleksandr Gavenko <gavenkoa@gmail.com> writes:
> On 2015-01-08, Robert Thorpe wrote:
...
> From my: http://sourceforge.net/u/gavenkoa/dot-emacs/ci/default/tree/INSTALL.rst
>
> I used this mostly for extend Cygwin/Mingw man/info for own directory (c:\home\usr\share)
>
> Setup MANPATH.
> --------------
prev parent reply other threads:[~2015-01-10 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 22:48 Directories for Ezwinports Robert Thorpe
2015-01-07 23:24 ` Óscar Fuentes
2015-01-08 3:40 ` Eli Zaretskii
2015-01-09 2:31 ` Robert Thorpe
2015-01-09 19:12 ` Oleksandr Gavenko
2015-01-10 21:08 ` Robert Thorpe [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=87lhlaibrr.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=gavenkoa@gmail.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).