Re: emacs -nw keypad and tpu-edt.el

> Date: Wed, 27 May 2009 16:05:25 -0400 > From: Ken Brown > > On 5/27/2009 3:36 PM, Tim Adye wrote: > > I just checked this on another machine that still had the old emacs 21.2 > > (and > > had recently had a fresh Cygwin install, and I applied the latest changes > > before testing). Before upda

Re: emacs -nw keypad, tpu-edt.el, and C-h

On 5/28/2009 3:48 AM, Eli Zaretskii wrote: What I can suggest at this point is send a formal bug report about this with "M-x report-emacs-bug RET". Tim, You're probably in the best position to do this, since I've never used tpu-edt. Alternatively, tell me precisely what steps to perform to

where is net/ethernet.h

Moin, I try to compile ptunnel. This is an application that tunnels a tcp connection through an icmp ping. Therefor, net/ethernet.h and pcap.h is required. In which packages are they? How can I find this out? I suppose that some files more are missing. Thanks -- |Michael Renner E-mail: m

Re: emacs -nw keypad, tpu-edt.el, and C-h

Ken Brown: > A separate issue that has arisen in this thread is that when emacs runs > in a cygwin terminal [*], it sees C-h as DEL instead of as the help key. > Can someone familiar with cygwin terminals help with this?  I'm speculating > again (bad habit), but it seems that the keycodes are being

limited connection numbers to X?

Hi, after opening about 15 to 20 connection to X, all further connection will end with an error "can't connect to X server" since I have lot of vim and xterm opened I must close some to open new ones... is it a known feature? it happens only on cygwin1.7 JLM -- KISS! (Keep It Simple, Stupid!) (ga

Re: where is net/ethernet.h

On Thu, May 28, 2009 at 03:41:33PM +0200, Michael Renner wrote: >Moin, > >I try to compile ptunnel. This is an application that tunnels a tcp connection >through an icmp ping. > >Therefor, net/ethernet.h and pcap.h is required. In which packages are they? >How can I find this out? I suppose that

Re: emacs -nw keypad, tpu-edt.el, and C-h

On 5/28/2009 10:02 AM, Andy Koppe wrote: There's an ancient and pointless argument about whether the Backspace key should send ^H (0x08) or ^? (0x7F). I was asking something slightly different: Can cygwin terminals be configured so that emacs can tell the difference between the Backspace key

Re: SSH client not starting

Any luck yet at getting an answer to this? Bill McCormick wrote: Dave Korn wrote: Bill McCormick wrote: Dave Korn wrote: Bill McCormick wrote: Looks like I don't have the zlib0 (or devel). I've tried a number of reinstalls with no change. What can I do? Run setup.exe and manually select

1.7.0-48: [BUG] Passing characters above 128 from bash command line

Hi Cygwin 1.7 developers, I think I've encountered bug in cygwin 1.7.0-48 on WinXP 32-bit. It seems that passing a character on the command line (from either ash.exe or bash.exe) that is greater than 127 to a native win32 process results in arguments being truncated. Hopefully you can reprod

Re: SSH client not starting

Bill McCormick wrote: Bill McCormick wrote: Dave Korn wrote: silly mistakes like having setup.exe running in download rather than download-and-install mode, or if you have multiple installations you've upgraded one and are testing the other, that sort of thing can easily happen... Nope. Sing

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

Edward Lam wrote: Hi Cygwin 1.7 developers, I think I've encountered bug in cygwin 1.7.0-48 on WinXP 32-bit. It seems that passing a character on the command line (from either ash.exe or bash.exe) that is greater than 127 to a native win32 process results in arguments being truncated. Hopef

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

Hi Larry, > This sounds allot like this report to me: > > I don't think it's the same bug because if I replace copyright.txt with a single printable character (eg. c), then it works. Regards, -Edward Larry Hall (Cygwin) wrote: Edward Lam w

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

PS. In case you haven't noticed, copyright.txt is not a long file. It consists of a single byte, 0xA9. Edward Lam wrote: Hi Larry, > This sounds allot like this report to me: > > I don't think it's the same bug because if I replace copyri

Re: emacs -nw keypad, tpu-edt.el, and C-h

On Thu, May 28, 2009 at 11:00 AM, Ken Brown wrote: > On 5/28/2009 10:02 AM, Andy Koppe wrote: >> >> There's an ancient and pointless argument about whether the Backspace >> key should send ^H (0x08) or ^? (0x7F). > > I was asking something slightly different: No, you were asking the same thing, y

Re: SSH client not starting

Larry Hall (Cygwin) wrote: Bill McCormick wrote: Bill McCormick wrote: Dave Korn wrote: silly mistakes like having setup.exe running in download rather than download-and-install mode, or if you have multiple installations you've upgraded one and are testing the other, that sort of thing can e

Re: SSH client not starting

Larry Hall (Cygwin) wrote: > Bill McCormick wrote: >>> Nope. Single install. Did the download 1st then ran the install from >>> the download. > > Try installing directly from the Internet. > > I know. Try it anyway. Bill McCormick wrote: > That works. > > I won't ask. I will. Larry, is thi

Re: emacs -nw keypad, tpu-edt.el, and C-h

>> Can cygwin terminals be >> configured so that emacs can tell the difference between the Backspace key >> and "pressing h while holding down the control key"? > > "pressing h while holding down the control key" produces ^H (0x08). > By default, this is also what backspace sends.  As Andy says, ma

Re: limited connection numbers to X?

jean-luc malet wrote: Hi, after opening about 15 to 20 connection to X, all further connection will end with an error "can't connect to X server" since I have lot of vim and xterm opened I must close some to open new ones... is it a known feature? it happens only on cygwin1.7 This is probably b

Re: SSH client not starting

Dave Korn wrote: Larry Hall (Cygwin) wrote: Bill McCormick wrote: Nope. Single install. Did the download 1st then ran the install from the download. Try installing directly from the Internet. I know. Try it anyway. Bill McCormick wrote: That works. I won't ask. I will. Larry, is th

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

On Thu, May 28, 2009 at 7:28 PM, Edward Lam wrote: > PS. In case you haven't noticed, copyright.txt is not a long file. It > consists of a single byte, 0xA9. Did you try utf-8 encoding copyright.txt? Perhaps your locale is utf-8 and the encoder fails. -- Unsubscribe info: http://cygwin.com/

Re: emacs -nw keypad, tpu-edt.el, and C-h

On 5/28/2009 1:10 PM, Andy Koppe wrote: Could the default for the terminals be changed? Yes, easily, but only at the cost of breaking any applications that always expect ^H for Backspace. Sorry, I guess I haven't been expressing myself very well. I wasn't suggesting any particular course of a

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

Alexey Borzenkov wrote: On Thu, May 28, 2009 at 7:28 PM, Edward Lam wrote: PS. In case you haven't noticed, copyright.txt is not a long file. It consists of a single byte, 0xA9. Did you try utf-8 encoding copyright.txt? Perhaps your locale is utf-8 and the encoder fails. How is one supposed

Re: emacs -nw keypad, tpu-edt.el, and C-h

> Sorry, I guess I haven't been expressing myself very well.  I wasn't > suggesting any particular course of action, and I certainly don't want to > break other applications. No worries. I was just trying to explain why the proper and obvious fix of switching the backspace defaults to ^? might be

Re: emacs -nw keypad, tpu-edt.el, and C-h

On 5/28/2009 5:14 PM, Andy Koppe wrote: And then there's the problem that the Cygwin console can't be changed to ^?. Emacs doesn't work well in the Cygwin console anyway, for a variety of reasons. I'll add that to the README and to the announcement when I release the next version. (FWIW, I'

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

On Wed, May 27, 2009 at 10:32 PM, Karl M wrote: > >> Date: Wed, 27 May 2009 21:26:36 -0600 >> Subject: Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path >> From: alfvaen >> You seem to be missing '/usr/bin' and '/usr/lib'. There was talk about some of this changing though in my

Re: emacs -nw keypad, tpu-edt.el, and C-h

Ken Brown wrote: On 5/28/2009 5:14 PM, Andy Koppe wrote: And then there's the problem that the Cygwin console can't be changed to ^?. Emacs doesn't work well in the Cygwin console anyway, for a variety of reasons. I'll add that to the README and to the announcement when I release the next v

Re: emacs -nw keypad, tpu-edt.el, and C-h

On 5/28/2009 5:41 PM, Larry Hall (Cygwin) wrote: Ken Brown wrote: On 5/28/2009 5:14 PM, Andy Koppe wrote: And then there's the problem that the Cygwin console can't be changed to ^?. Emacs doesn't work well in the Cygwin console anyway, for a variety of reasons. I'll add that to the README

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

On Thu, May 28, 2009 at 03:37:39PM -0600, Aaron Humphrey wrote: >On Wed, May 27, 2009 at 10:32 PM, Karl M wrote: >> >>> Date: Wed, 27 May 2009 21:26:36 -0600 >>> Subject: Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path >>> From: alfvaen >>> > You seem to be missing '/usr/bin' and '

Re: OpenSSH server installation error on Windows Vista Business/Ultimate

David, thanks for the suggestion. I will be eager to try that after I come back later next week. I will update you on what I get. Paul. > OpenSSH server installation error on Windows Vista Business/Ultimate > 150955 by: Paul August > 150964 by: "David Christensen" > > -Inline

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

So, in the end, reinstalling didn't do much. And I got a bunch of "Cannot open (null) for reading" (error not guaranteed to be accurate), usually when it was trying to install gzipped man pages or something. (Times like these I wonder why I persist in downloading every cygwin package on the mirro