On 2/1/2016 6:38 PM, Richard Heintze wrote:
(1) OK, I did that and I saw the 24.5-3. However, when I got to help about
emacs, it says 24.5-1! did I do wrong?
I don't think it says 24.5-1. It says 24.5.1. The ".1" is a build
counter, which has nothing to do with Cygwin's release number 3.
[Please keep the discussion on the mailing list so that others can
benefit from it.]
On 1/25/2016 11:48 PM, Richard Heintze wrote:
How do I know I have your new version? Does it not take a while to propagate to
all those servers? Is there a special place/server I can download and install
it?
On 1/21/2016 8:18 AM, Ken Brown wrote:
In the meantime, I'm looking into patching emacs so that the Cygwin
build will accept Windows file names, at least under some circumstances.
If I can do that without breaking anything else, I'll put out a test
release.
This is done now. Please test.
Ke
On 1/20/2016 9:20 PM, Richard Heintze wrote:
On 1/19/2016 6:34 PM, Richard Heintze wrote:
Regarding my choice of terms: I was trying use terms consistent with that old
link
"https://cygwin.com/ml/cygwin/2011-02/msg00416.html";.
That message doesn't even mention emacs. That's why I said in m
>On Tuesday, January 19, 2016 5:26 PM, Ken Brown wrote:
>[Please don't top post.]
>On 1/19/2016 6:34 PM, Richard Heintze wrote:
>> Regarding my choice of terms: I was trying use terms consistent with that
>> old link
>> "https://cygwin.com/ml/cygwin/2011-02/msg00416.html";.
>That message doe
On 1/20/2016 4:19 AM, Andrey Repin wrote:
>
> I think it would be easier to just set Cygwin to use $USERPROFILE as $HOME.
> Then $HOME would be a POSIX path you can use in the emacs config.
>
>
You can do that before you start Cygwin or even in the /etc/profile.d
scripts. But I agree that $US
On 1/20/2016 4:19 AM, Andrey Repin wrote:
Greetings, Ken Brown!
(2) I was using $USERPROFILE as an example. We have dozens of these
environment variables pointing to dozens directories. They enable us to
type in the same file name to emacs's find file (ctrl-x-ctrl-f) regardless
of who is logged
Greetings, Ken Brown!
>> (2) I was using $USERPROFILE as an example. We have dozens of these
>> environment variables pointing to dozens directories. They enable us to
>> type in the same file name to emacs's find file (ctrl-x-ctrl-f) regardless
>> of who is logged in or which computer we are logg
[Please don't top post.]
On 1/19/2016 6:34 PM, Richard Heintze wrote:
Regarding my choice of terms: I was trying use terms consistent with that old
link
"https://cygwin.com/ml/cygwin/2011-02/msg00416.html";.
That message doesn't even mention emacs. That's why I said in my first
reply to you
On 1/19/2016 2:06 PM, Richard Heintze wrote:
Anyway, I'm getting very similar symptoms on cygwin64 with windows 10 with FSF
emacs 23.2, 24.2& 24.5.
By the way, some people might be confused by your phrase "FSF emacs".
You're talking about a native Windows build of emacs as opposed to a
Cygwi
On 1/19/2016 2:06 PM, Richard Heintze wrote:
Unfortunately, the following file name (for example) works with fsf emacs and
not Cygwin emacs-w32:
$USERPROFILE/Documents/hello.txt
Even some bash commands accept this but emacs-w32 does not.
I use these environment variables extensively to facili
On 1/16/2016 2:38 PM, Richard Heintze wrote:
On Friday, January 15, 2016 5:35 PM, Richard Heintze
wrote:
regarding: https://cygwin.com/ml/cygwin/2011-02/msg00416.html
I'm getting similar errors (see link below) but only on Windows 10 with Cygwin
64.
You seem to have omitted the link.
12 matches
Mail list logo
