I've updated mosh on x86 to the latest version 1.2.4, x86_64 not yet.
Changes largely include bug fixes, improved robustness, and added
platform support.
This reinstates the original perl wrapper, as the failing perl IO::Tty module
is not used anymore.
See http://mailman.mit.edu/pipermail/mosh-us
I'm having a great deal of difficulty getting my programs that use curses to
compile with Windows 8.1 64 bit. I've been
using/usr/x86_64-w64-mingw32/sys-root/mingw for the header and library
files. When the compiler couldn't find some of the necessary header files
that are in /usr/include, I copied
On 32-bit Cygwin the CVS package is at version 1.12.13 whereas on 64-bit Cygwin
it is at 1.11.23. The latter can handle proxy servers whereas the former
cannot, so I would prefer 1.12.13 on both.
I note that 1.11.23 (the last stable release) is quite a lot *newer* than
1.12.13 (the last feature
On 11/21/2013 15:57, Warren Young wrote:
On 11/21/2013 15:50, Warren Young wrote:
On 11/21/2013 15:13, casem wrote:
$ procps -V
Unknown HZ value! (632) Assume 1024.
Does the warning go away if you run
$ HZ=1024 procps -V
instead?
By the way, I tried it here and didn't get the compla
On 11/21/2013 15:50, Warren Young wrote:
On 11/21/2013 15:13, casem wrote:
$ procps -V
Unknown HZ value! (632) Assume 1024.
Does the warning go away if you run
$ HZ=1024 procps -V
instead?
By the way, I tried it here and didn't get the complaint.
It seems someone has set the HZ envi
On 11/21/2013 15:13, casem wrote:
$ procps -V
Unknown HZ value! (632) Assume 1024.
Does the warning go away if you run
$ HZ=1024 procps -V
instead?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygw
Hello, I just reinstalled the latest 64-bit Cygwin yesterday on my
Windows 8.1 machine. I installed the new procps 3.2.8-1 package as well
(thanks for making it available for 64-bit). Now when I run any procps
commands, I get this message:
"Unknown HZ value! (632) Assume 1024."
Versions:
$ una
I have some new information. I tried using
export CYGWIN="error_start=gdb -nw %1 %2"
and I was able to catch an abort in emacs-w32 that gave no abort dialog
box, similar to emacs-X11 aborts. The log from GDB is given below:
(gdb) continue
Continuing.
[Thread 5840.0x1220 exited with code 0]
Thanks for the assistance Ken, I appreciate it. I was able to uninstall
Symantec Endpoint Protection, so the only piece of software that I may
have from the BLODA list is now NVIDIA Geforce. I took your advice about
experimentation, and I discovered some more information.
It turns out that Ema
Hello,
I am about to create a silent install script to help automatically deploying
Cygwin. Actually the target environment are machines where users don't have
admin rights so Cygwin needs to be installed without administrator privileges. I
see in the documentation and FAQ that the --no-admin
10 matches
Mail list logo
