RE: RE: RE: RE: Two issues with Xwin
> It's not Zsh that's eating my Enter (or Tab) key but X (or maybe the > terminal emulator). It doesn't happen all the time but "often". I > can't find any pattern in this. I sometimes find that I have to wait 10-40 seconds or so until the completions are shown. Or, when I do a ls /usr/bin (for instance), sometimes I see the result immediately, sometimes it takes 10-15 seconds after pressing the enter key, until the files are displayed. Could be attributed in my case to networking issues (my $HOME is on a Samba-mounted netdrive), so it could be a timing/caching issue. But this does, of course, not explain why your two terminals should behave differently. You did not say how frequent this occurs. Could it be that it happens rarely enough, that just by accident you have observed it only with one terminal type, but not with the other? Does the X terminal sometimes "eat" other keys too when you are typing fast? And I still would find it worth a try - despite what has been suggested earlier in this thread - to see whether the same behaviour exists with bash (or other applications reading keystrokes). Ronald -- Ronald Fischer <[EMAIL PROTECTED]> Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: RE: RE: Two issues with Xwin
* Ronald Fischer (Wed, 29 Aug 2007 10:20:18 +0200) > > Thorsten wrote: > > I have two issues that I've been experiencing for quite a long time: > > > > * using a terminal and a shell I often have to enter Enter or Tab > > twice to get the desired effect. How come? [...] > At the time the OP had just mentioned the problem, I thought that indeed > the differences could be cygwin related: When I run my X11 rxvt (from > startxwin.bat), different dot files in my home directory are sourced > than when I start a shell from the command line (outside X). There is > no mystery about this and has to do with the rules according to which > the shells (bash, zsh,...) read their dot-files. > > But in the last mail, the OP said he has ONLY one dot-file, i.e. .zshrc, > (meaning it will be read in every interactive shell, be it login shell > or not) AND he is using zsh in both cases, AND he has no settings > related to > completion, AND still completion works in a different way in both cases. > To track down this mystery, I think it is worth digging down what other > configuration files (besides those in $HOME) might affect zsh. Since > I am not that big an zsh expert, and since no other posting so far > (unless > I missed one) gave any information about zsh, I think it was a > reasonable advice to post this issue to the zsh mailing list as well - > don't you think so? > > > Fine, > > they COULD have different zsh binaries sourcing different environment > > files, but it's far more likely that Cygwin/X is misbehaving than that > > Thorsten somehow managed to find a zsh binary that sometimes eats the > > enter key. > > As for the enter key, you are right. In his first posting, Thorsten > mentioned the "Enter or Tab" key "on the first try". Since both keys > are used in the context of completion, I guessed it was a completion > issue - and Thorsten at least did not directly contradict this. > > You seem to suggest that he meant that in *every* usage of enter > and tab, the first one has been eaten? If this were the case, it > would indeed change the picture, and maybe Thorsten could clarify > this issue. It's not Zsh that's eating my Enter (or Tab) key but X (or maybe the terminal emulator). It doesn't happen all the time but "often". I can't find any pattern in this. Sometimes I think that I'm just stupid and don't press that Enter key hard enough but that can't be the reason. Why would Konsole require the Enter key to be pressed "harder"?! I'm using Konsole (either via X forwarding or the Konsole Cygwin exe) so I don't whether it happens with other terminals. I don't use Rxvt under X because I looks very ugly and I can't make it display my preferred font (Dejavu Mono). Thorsten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: RE: RE: Two issues with Xwin
> Thorsten wrote: > I have two issues that I've been experiencing for quite a long time: > > * using a terminal and a shell I often have to enter Enter or Tab > twice to get the desired effect. How come? > > Ronald wrote: > > Which effect do you desire? (Filename completion, command > completion, ...)? > > Thorsten wrote: > > The desired effect for the Enter key would be to normal enter function > of a shell. Tab should do file and command completion. > ... > I don't think the content of $INPUTRC is relevant when talking about > Enter and Tab having no effect "on the first try". > ... > And I don't have any setting that would have the "do nothing on the > first enter; wait for the second enter" effect. > > Ronald wrote: > I guess you mean: "wait for the second *tab*" etc. > > > SO, my question to Ronald is: Have you read anything in this thread, > or just posted to it a lot? It's obviously NOT a zsh problem if it > doesn't happen in Windows RXVT but does happen in X11 RXVT. No need to start flaming though Yes, I am aware of these differences, and - to make it clear, just in case - it that I think of it neither as "cygwin problem" nor "zsh problem" in the sense of "problem" meaning a possible bug in cygwin and/or zsh; what I wanted to say is that given that information posted (and I think I read every posting to this thread), I thought that maybe people at the zsh mailing list could better help here (zsh - the last time I was subscribed to it - was a very high volume mailing list, even more than cygwin, and many of the subscribers were actually using cygwin). At the time the OP had just mentioned the problem, I thought that indeed the differences could be cygwin related: When I run my X11 rxvt (from startxwin.bat), different dot files in my home directory are sourced than when I start a shell from the command line (outside X). There is no mystery about this and has to do with the rules according to which the shells (bash, zsh,...) read their dot-files. But in the last mail, the OP said he has ONLY one dot-file, i.e. .zshrc, (meaning it will be read in every interactive shell, be it login shell or not) AND he is using zsh in both cases, AND he has no settings related to completion, AND still completion works in a different way in both cases. To track down this mystery, I think it is worth digging down what other configuration files (besides those in $HOME) might affect zsh. Since I am not that big an zsh expert, and since no other posting so far (unless I missed one) gave any information about zsh, I think it was a reasonable advice to post this issue to the zsh mailing list as well - don't you think so? > Fine, > they COULD have different zsh binaries sourcing different environment > files, but it's far more likely that Cygwin/X is misbehaving than that > Thorsten somehow managed to find a zsh binary that sometimes eats the > enter key. As for the enter key, you are right. In his first posting, Thorsten mentioned the "Enter or Tab" key "on the first try". Since both keys are used in the context of completion, I guessed it was a completion issue - and Thorsten at least did not directly contradict this. You seem to suggest that he meant that in *every* usage of enter and tab, the first one has been eaten? If this were the case, it would indeed change the picture, and maybe Thorsten could clarify this issue. Ronald -- Ronald Fischer <[EMAIL PROTECTED]> Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: RE: RE: Two issues with Xwin
Thorsten wrote: I have two issues that I've been experiencing for quite a long time: * using a terminal and a shell I often have to enter Enter or Tab twice to get the desired effect. How come? Ronald wrote: Which effect do you desire? (Filename completion, command completion, ...)? Thorsten wrote: The desired effect for the Enter key would be to normal enter function of a shell. Tab should do file and command completion. ... I don't think the content of $INPUTRC is relevant when talking about Enter and Tab having no effect "on the first try". ... And I don't have any setting that would have the "do nothing on the first enter; wait for the second enter" effect. Ronald wrote: I guess you mean: "wait for the second *tab*" etc. SO, my question to Ronald is: Have you read anything in this thread, or just posted to it a lot? It's obviously NOT a zsh problem if it doesn't happen in Windows RXVT but does happen in X11 RXVT. Fine, they COULD have different zsh binaries sourcing different environment files, but it's far more likely that Cygwin/X is misbehaving than that Thorsten somehow managed to find a zsh binary that sometimes eats the enter key. If you can't take the time to read a thread, you really oughtn't post to it. > Maybe this is the point where you should repost this problem to the zsh > folks. > Not only it doesn't look that much like a Cygwin issue to me, but I > remember > that on the zsh mailing list > there are also quite a few Cygwin users hanging around Again, read better, or at least research. Thorsten IS one of the Cygwin people who hangs around the zsh mailing lists. The only thing worse than no answer to a question is a wrong answer that keeps being repeated. Do Thorsten a favor and stop talking. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: RE: RE: Two issues with Xwin
> * Ronald Fischer (Mon, 27 Aug 2007 15:57:34 +0200) > > This suggest that different dot-files are sourced in the two cases. > > When I run bash (in my case) either from cmd or started by XWin, I > > also have differences in which dot-files are sourced, so this is the > > first place you might want to look. > > There is just one configuration file in this case: ~/.zshrc. H this should be sourced every time you have an interactive shell. > And I > don't have any setting that would have the "do nothing on the first > enter; wait for the second enter" effect. I guess you mean: "wait for the second *tab*" etc. In this case, the correct behaviour should *always* be (I think) to show that part of the completion, which is unique, on the first press of tab, and show a list of all possible completions on the second press of tab. If it is not due to different settings in your shells, I have no idea why anymore why both shells behave different (stupid question: You are sure that you have the same zsh called in both cases? What does echo $ZSH_VERSION say in rxvt, respectively CMD window?) Maybe this is the point where you should repost this problem to the zsh folks. Not only it doesn't look that much like a Cygwin issue to me, but I remember that on the zsh mailing list (http://zsh.dotsrc.org/Doc/Release/zsh_2.html#SEC6), there are also quite a few Cygwin users hanging around, so your problem will for sure be understood there. Ronald -- Ronald Fischer <[EMAIL PROTECTED]> Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: RE: Two issues with Xwin
* Ronald Fischer (Mon, 27 Aug 2007 15:57:34 +0200) > This suggest that different dot-files are sourced in the two cases. > When I run bash (in my case) either from cmd or started by XWin, I > also have differences in which dot-files are sourced, so this is the > first place you might want to look. There is just one configuration file in this case: ~/.zshrc. And I don't have any setting that would have the "do nothing on the first enter; wait for the second enter" effect. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: RE: Two issues with Xwin
> The desired effect for the Enter key would be to normal enter > function > of a shell. Tab should do file and command completion. > > > Which shell? > > zsh > > > How did you configure it? (i.e. if you are talking about readline > > functionality, what's the content of your .inputrc, and did > you make sure it gets > > read?). > > I don't think the content of $INPUTRC is relevant when talking about > Enter and Tab having no effect "on the first try". They do for a shell which uses readline for completion, because the behaviour (show the completions immediately, or beep and show them on the second tab) is defined there. AFIK, the completion system of zsh is more flexible (read: there are more things to consider) than with bash (which just uses what readline thinks about completion). For your case, the setting of the variables AUTO_LIST and LIST_AMBIGUOUS could apply here, and maybe you have to unset LIST_BEEP to (I'm not so deep into zsh that I could tell this, so you would have to go through the man page or ask this in the zsh mailing list). > Anyway, I have no > problem with that in rxvt or cmd - only in X. This suggest that different dot-files are sourced in the two cases. When I run bash (in my case) either from cmd or started by XWin, I also have differences in which dot-files are sourced, so this is the first place you might want to look. Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
