Re: Newbie: translation does not work - solved
On Tue, Oct 13, 2009 at 9:03 AM, wrote:
> Problem solved. My .Xdefault file was in the wrong directory.
Uh, that wasn't your only problem...
> - Mail transféré -
> De: phi...@free.fr
> À: "cygwin-xfree"
> Envoyé: Mardi 13 Octobre 2009 13:39:19 GMT +01:00 Amsterdam / Berlin / Berne
> / Rome / Stockholm / Vienne
> Objet: Newbie: translation does not work
>
> Hi,
>
> I have create this translation in my .Xdefault file
>
> *VT100.translation: #override \
^ ^
>:F1 string("Hello world") string(0x0d)
^
You had at least 3 typos afaics; this should have been
*VT100.Translations: #override \
F1: string("Hello world") string(0x0d)
> Any suggestions?
~Matt
--
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: Unable to initiate X server
On Sun, Sep 20, 2009 at 6:17 PM, cs liew wrote: > Hi, > > I installed Cygwin and I tried to initiate X server but an error message > showed up which says "A fatal error has occurred and Cygwin/X will now exit. > Please open /var/log/XWin.0.log for more information." > > So what should I do to fix this? Please help! > > Thanks! Try opening /var/log/XWin.0.log - it probably has more information. ~Matt -- 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: Background processes with Cygwin
http://www.cygwin.com/acronyms/#PCYMTNQREAIYR On Sat, Apr 4, 2009 at 9:50 PM, Peter Farley wrote: > > --- On Fri, 4/3/09, Jeff Irwin wrote: Don't quote headers like this. It's not useful to anyone, and it feeds the spammers. >> From: Jeff Irwin >> Subject: Background processes with Cygwin >> To: x...@xxx.xxx >> Date: Friday, April 3, 2009, 2:48 PM > http://www.cygwin.com/acronyms/#PCYMTWLL - Reformatted > PMFJI here, but if you log out of Cygwin, then the Cygwin process terminates. > Why would you think that a process started under Cygwin could survive the > termination of Cygwin? That just doesn't make sense, even to this raw > newbie. You're missing something big. Cygwin isn't a process. It's a DLL that provides a UNIX-like environment. You don't terminate cygwin, you terminate a shell that's using the Unix emulation provided by cygwin1.dll. > Among other things, the whole *ix environment that Cygwin provides would be > gone, so how could your process possibly continue? This isn't "real" *ix, > it's *ix facilities provided under the control of another quite different > (and generally more hostile) OS environment. The *ix facilities are provided by a DLL, not by a process, and the applications can continue running after the shell exits, just like in any other *ix - the DLL didn't go away, after all. > Maybe I'm missing something crucial in my understanding of how Cygwin and > Windows operate. If so, I'd appreciate a cure for my ignorance. Hopefully this clears things up. Unfortunately, I'm not sure why things aren't working for the OP. In any event, switching to the main cygwin list instead of the cygwin-xfree list (which is only for X11 related issues) would probably help get him the help he needs. ~Matt -- 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: FW: Cygwin installation
Yuck. http://www.cygwin.com/acronyms/#PCYMTWLL Reformatted. Stephen Mcgowan wrote: > I am writing as I'm having trouble with setting up my cygwin using > a windows vista operating system. > > I have downloaded and installed cygwin to my C:\ and for my course > have been asked to right click the icon and go into properties. What icon? Seems you're changing the properties for the link to cygwin.bat for some reason... what are you trying to accomplish? > For the "Target" set it to C:\cygwin\cygwin.bat and for the "Start > In:" set it to C:\cygwin\usr\X11R6\bin\startxwin.bat (see picture). Yep. Which means you want the application (cygwin.bat) to start in the directory c:\cygwin\usr\X11R6\bin\startxwin.bat > The thing is, I set these, and the picture shows I have located the > startxwin.bat file on the right hand side, but I receive the following > error message: > > "The folder C:\cygwin\usr\X11R6\bin\startxwin.bat" specified in the > Start In box is not valid. Make sure the folder exists and the path is > correct." Because it's a file, not a folder. An application starts in a certain directory; it can't start in a file. > Any assistance or advice on this matter would be greatly appreciated, > > Many Thanks, > > Stephen McGowan I'm not really even sure what you're trying to do. ~Matt -- 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: Bad XTerm Vim coloring
On Mon, Nov 24, 2008 at 8:59 PM, Thomas Dickey wrote: > On Mon, 24 Nov 2008, Thomas Dickey wrote: > >> I'd expect that vim is asking xterm for the strings that correspond to >> different function-keys. In ctlseqs.txt this text covers the response: > > ...reading vim's source code (7.1 at hand...), there doesn't seem to be an > obvious way to turn off the feature (the "+termresponse"). There's no obvious way to turn it off, but it can be turned off... vim --cmd 'set t_RV=' for a single vim session, or echo 'set t_RV=' >>~/.vimrc for all vim sessions. Not sure why it would be breaking, though... and I don't presently have a cygwin installation to test this myself... ~Matt -- 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: excuse this test
On Thu, Nov 13, 2008 at 1:52 PM, Paul McFerrin wrote: > excuse this test, it *should* get rejected The cygwin lists are public, anyone can post to them even if not subscribed. This wasn't a useful test to see if your unsubscribe worked. ~Matt -- 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: Window icons in multi-window mode
On Fri, Aug 1, 2008 at 6:48 PM, Raul Acevedo wrote: >> I don't know any general answer, but for emacs I think you can get a >> special icon by putting >> >> emacs*bitmapIcon: on >> >> in your .Xdefaults file. If that is the solution, you would need either to do "xrdb -merge ~/.Xdefaults" or to restart the x server in order to load the change. That being said, vim ftw. ~Matt -- 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: deleted by mistake .bashrc file in C:\cygwin\home\setup after install
Obviously not cygwin-specific, and I don't have a cygwin computer in
front of me at the moment, so I'm not even positive that this applies
on cygwin - but on most UNIX systems, you could run
cp /etc/skel/.bashrc ~/.bashrc
Again, I'm not positive that cygwin even has a /etc/skel, but most
UNIX systems copy the files in /etc/skel/ into every new user's home
folder when it's created. Running that command would be the
equivalent of the copy that the system did behind-the-scenes when
setting up your home folder.
~Matt
On 4/29/07, Ken Smith <[EMAIL PROTECTED]> wrote:
Garrett Cooper wrote:
> Tomczak wrote:
>> Hi
>>
>> I did install cygwin and Grass on windows XP at the weekend and
>> accidentally
>> deleted .bashrc file in C:\cygwin\home\setup and the file is not in my
>> recycle bin.
>>
>> Can someone advise how i can get it back from the downloaded install
>> files.
>> I was installing Grass 6.2.1 Win/Grass with cygwin. i used the latest
>> cygwin
>> download from the setup program.
>>
>> Also would like to know to edit it as i know very little about unix.
>>
>> Thanks in Advance
>>
>> Thierry
>
> First off, you accidentally emailed this to the wrong list.
>
> Second off, honestly if it wasn't produced when you first started
> cygwin up and you didn't back it up, then you are (unfortunately) at
> fault for your own file deletion. AFAIK there isn't any way to get it
> back.
>
> -Garrett
>
> {snip}
>
>
Another approach might be to log on as another user and let the system
generate a new .bashrc and then copy the file over. As it happens on my
system the .bashrc is largely commented out as follows.
# base-files version 3.2-1
# User dependent .bashrc file
# See man bash for more options...
# Don't wait for job termination notification
# set -o notify
# Don't use ^D to exit
# set -o ignoreeof
# Don't put duplicate lines in the history.
# export HISTCONTROL=ignoredups
# Some example alias instructions
# alias less='less -r'
# alias rm='rm -i'
# alias whence='type -a'
# alias ls='ls -F --color=tty'
# alias dir='ls --color=auto --format=vertical'
# alias vdir='ls --color=auto --format=long'
# alias ll='ls -l'
# alias la='ls -A'
# alias l='ls -CF'
# Some example functions
# function settitle() { echo -n "^[]2;[EMAIL PROTECTED];[EMAIL PROTECTED]"; }
Hope that helps
Ken
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
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/
--
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: Problems with terminal -tn setting TERM variable
Oh, I'm sorry, I misread. Well, then, that makes perfect sense. My mistake, Igor. :) Can anyone tell me who the xterm maintainer is? I was under the impression that the entirety of Cygwin/X is unmaintained. ~Matt On 11/4/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: On Fri, 3 Nov 2006, Matt Wozniski wrote: > On 11/3/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: <http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Thanks. > > According to the xterm manpage, "This terminal type must exist in the > > terminal database (termcap or terminfo, depending on how xterm is > > built) and should have li# and co# entries. If the terminal type is > > not found, xterm uses the built-in list ``xterm'', ``vt102'', etc." > > > > "xterm -tn ansi" and "xterm -tn vt100" both work. You need to look at > > your terminal database and figure out why xterm is not picking it up. > > Well, mystery solved, it's using termcap instead of terminfo, but why > would on earth would two Cygwin xterm packages (mine and Igor's) use > two different terminal capability databases? The man page says that > it depends on how it was built, but how could the two packages have > been built differently? Umm, actually, what I said was that I *could* reproduce your behavior. My xterm also uses /etc/termcap. No mystery here. Both "ansi" and "vt100" are in /etc/termcap, and "xterm-16color" isn't. > Igor: Does "grep '^xterm' /etc/termcap" give you more than just one > line defining xterm-r6 and xterm? I'm just trying to figure out if > yours is also using termcap and your termcap entry covers > xterm-16color, or if yours is using terminfo like it ought to be. My termcap only has one entry for xterm. As for whether xterm should be using terminfo, you might want to ask the xterm maintainer to rebuild the package. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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/ -- 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: Problems with terminal -tn setting TERM variable
On 11/3/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: According to the xterm manpage, "This terminal type must exist in the terminal database (termcap or terminfo, depending on how xterm is built) and should have li# and co# entries. If the terminal type is not found, xterm uses the built-in list ``xterm'', ``vt102'', etc." "xterm -tn ansi" and "xterm -tn vt100" both work. You need to look at your terminal database and figure out why xterm is not picking it up. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" Well, mystery solved, it's using termcap instead of terminfo, but why would on earth would two Cygwin xterm packages (mine and Igor's) use two different terminal capability databases? The man page says that it depends on how it was built, but how could the two packages have been built differently? Igor: Does "grep '^xterm' /etc/termcap" give you more than just one line defining xterm-r6 and xterm? I'm just trying to figure out if yours is also using termcap and your termcap entry covers xterm-16color, or if yours is using terminfo like it ought to be. Thanks for any insight anyone can provide. ~Matt -- 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/
Problems with terminal -tn setting TERM variable
Sorry for the crosspost - I posted this on the Cygwin list last week, but didn't get a response, and realized that it probably belonged better on this list, so I'm trying again. I'm sorry if there's an easy solution that I haven't found yet, but I'm wondering if anyone else is experiencing the same problem with Cygwin/X's xterm as I am. xterm -tn doesn't seem to properly set up the TERM variable. For example: xterm -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x' pops up a Cygwin/X xterm window containing TERM=xterm Whereas rxvt -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x' pops up a Cygwin/X rxvt window containing TERM=xterm-16color Can anyone else confirm this behavior, or offer a suggestion on how to deal with this behavior? I want to use xterm, since I couldn't get the same level of unicode support in rxvt cygwin native, rxvt cygwin x unicode, or rxvt cygwin. I also don't want to explicitly set TERM in one of my dot files, since I use the same ones on many computers. Thanks in advance for any help! ~Matt Wozniski Cygwin Configuration Diagnostics Current System Time: Fri Nov 03 10:21:18 2006 Windows XP Professional Ver 5.1 Build 2600 Service Pack 2 Path: c:\cygwin\usr\local\bin c:\cygwin\bin c:\cygwin\bin c:\cygwin\usr\X11R6\bin . c:\Program Files\Reflection c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\Sybase\DLL c:\Sybase\BIN c:\Program Files\Sybase\Sybase Central\win32 c:\Sybase\ASEP Output from c:\cygwin\bin\id.exe (nontsec) UID: 112940(woznismj) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 547(Power Users) 545(Users) 10545(mkgroup-l-d) Output from c:\cygwin\bin\id.exe (ntsec) UID: 112940(woznismj) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 547(Power Users) 545(Users) 10545(mkgroup-l-d) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS HOME = '/cygdrive/c/Documents and Settings/woznismj' PWD = '/cygdrive/c/Documents and Settings/woznismj' USER = 'woznismj' MAKE_MODE = 'unix' ALLUSERSPROFILE = 'C:\Documents and Settings\All Users' APPDATA = 'C:\Documents and Settings\woznismj\Application Data' CLASSPATH = 'C:\Sybase\ASEP\Monclass.zip;C:\Sybase\ASEP\3pclass.zip;' CLIENTNAME = 'Console' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' COMPUTERNAME = '197PRGRCOOP' COMSPEC = 'C:\WINDOWS\system32\cmd.exe' CYGWIN_ROOT = '\cygwin' EDITOR = 'vim' FP_NO_HOST_CHECK = 'NO' HOMEDRIVE = 'C:' HOMEPATH = '\Documents and Settings\woznismj' INCLUDE = 'C:\Sybase\INCLUDE' LIB = 'C:\Sybase\LIB' LOGONSERVER = '\\MLAS001' NUMBER_OF_PROCESSORS = '1' OS = 'Windows_NT' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = 'x86' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 2 Stepping 4, GenuineIntel' PROCESSOR_LEVEL = '15' PROCESSOR_REVISION = '0204' PROGRAMFILES = 'C:\Program Files' PROMPT = '$P$G' SESSIONNAME = 'Console' SYBASE = 'C:\Sybase' SYSTEMDRIVE = 'C:' SYSTEMROOT = 'C:\WINDOWS' TEMP = '/cygdrive/c/DOCUME~1/woznismj/LOCALS~1/Temp' TMP = '/cygdrive/c/DOCUME~1/woznismj/LOCALS~1/Temp' USERDNSDOMAIN = 'DUPONTNET.NET' USERDOMAIN = 'DUPONTNET' USERPROFILE = 'C:\Documents and Settings\woznismj' VISUAL = 'vim' WINDIR = 'C:\WINDOWS' TERM = 'xterm' COLORFGBG = 'default;default;0' DISPLAY = ':0' WINDOWID = '6832192' TZ = 'EST5EDT4,M4.1.0/2,M10.5.0/2' LOGNAME = 'woznismj' SHLVL = '1' OLDPWD = '/cygdrive/c/Documents and Settings/woznismj' PAGER = 'less' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' CVS_RSH = '/bin/ssh' PKG_CONFIG_PATH = '/usr/X11R6/lib/pkgconfig' SHELL = '/usr/bin/zsh' PRINTER = '\\mlps001\197-2' LD_LIBRARY_PATH_64 = '/cygdrive/c/Documents and Settings/woznismj/projects/grs/DDPCgrs/lib:' NO_TTY_MOUSE = '1' MINICOM = '-w -z -C /dev/null -c off' LS_COLORS = 'no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tif
