public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygwin-xfree@cygwin.com Subject: Re: Thanks and a question Date: Tue, 13 Jan 2004 20:23:00 -0000 [thread overview] Message-ID: <400453BA.3050402@msu.edu> (raw) In-Reply-To: <1074024395.12868.5.camel@david.internal.NorcrossGroup.com> Greg, Greg Freemyer wrote: > On Tue, 2004-01-13 at 14:45, Igor Pechtchanski wrote: > >>On Tue, 13 Jan 2004, Greg Freemyer wrote: >> >> >>>Harold, >>> >>>Your work on the clipboard with xdmcp capability is greatly >>>appreciated. >>> >>>>From my minimal testing it works great. >>> >>>Now that the startup batch script can be simplified to a one liner, I >>>want to directly invoke "Xwin -query" from my desktop without first >>>launching a bash console. >>> >>>ie. I currently launch a bash script, then run my batch script. It >>>would be nice to instead just double click an icon on my desktop. >>> >>>I have setup a shortcut to XWin.exe on my desktop, but it is not >>>working. >>> >>>Currently I am getting an error about a missing DLL. Unfortunately I >>>need dlls from both /cygwin/bin and /cygwin/usr/X11R6/bin, so just >>>changing the startup directory is not quite enough. >>> >>>Is there a recommended way to get this to work? >>> >>>ie. Adding a shortcut (or a cygwin hardlink) to the cygcygipc-2.dll in >>>X11R6/bin >>> >>>Thanks Again >>>Greg >> >>Greg, >> >>Just add both c:/cygwin/bin and c:/cygwin/usr/X11R6/bin to the end of your >>Windows PATH variable. >> Igor > > > Thanks Igor, > > It worked great, and Harold this just seems cleaner than the approach > you gave. This way the windows shortcut is pointing directly at > XWin.exe and there is no excess overhead associated with starting a bash > shell up. Since when did batch files require bash shells? Did you notice the .bat extension? Those are run by Windows and let me tell you, ain't no way you are going to avoid the overhead of running Windows :) > If anyone cares, the PATH variable for Win2K is set by > right clicking 'my computer' > properties > advanced tab > environment variables > system variables Or press [Windows Key] + PrinttScreen and resume at the Advanced tab step. The reason I will never advise users to set their PATHs like this is because we will inevitably have users that install once to d:\cygwin, then remove that installation and reinstall later to c:\cygwin, but forget that they have done this. They will then insist that they setup the PATH as described (without double-checking to verify, of course), and will persist at complaining about how this doesn't work. Making a shortcut to the batch file sets the path based on the location of the batch file, which cannot be screwed up; if a user had a dead shortcut they would get a warning about not being able to find the target of the shortcut instead of some vague message about a DLL not being found. There is a method to this madness... Harold
prev parent reply other threads:[~2004-01-13 20:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-13 19:35 Greg Freemyer 2004-01-13 19:44 ` Harold L Hunt II 2004-01-13 19:45 ` Igor Pechtchanski 2004-01-13 20:16 ` Greg Freemyer 2004-01-13 20:23 ` Harold L Hunt II [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=400453BA.3050402@msu.edu \ --to=huntharo@msu.edu \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).