From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Window Maker issues, launching from cygwin
Date: Tue, 27 Jun 2017 21:42:00 -0000 [thread overview]
Message-ID: <1adcd353-b759-d423-3612-78b88a1fa7e1@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAJ9=ABrvn8gGsca5UUJ00_j9vmnngxz8-vX2rGM6EJ4-KXiZvQ@mail.gmail.com>
On 2017-06-27 14:05, David DLC wrote:
> /etc/X11/xinit/xinitrc-common: line 20: [: too many arguments
> Excessive file argument "Cruz/.Xresources"
> 1 error in preprocessor.
> /etc/X11/xinit/xinitrc: line 20: [: too many arguments
Fix the above two lines 20 in /etc/X11/xinit/xinitrc{,-common}
by adding double quotes around the string containing $HOME, which
might be like the lines below, from the only system script I could
find containing $HOME, where the whole file name is double quoted,
including the embedded $HOME:
$ fgrep '$HOME' /etc/profile.d/bash_completion.sh
[ -r "${XDG_CONFIG_HOME:-$HOME/.config}/bash_completion" ] && \
. "${XDG_CONFIG_HOME:-$HOME/.config}/bash_completion"
If your scripts are similar, such as:
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
then you need to double quote both the test and use as in:
[ -r "$HOME/.Xresources" ] && xrdb "$HOME/.Xresources"
and do the same kind of change in both files.
Many admins, packages, and distros have already made these kinds of
fixes, as more people are using Windows or Mac based home directories
which may have "friendlier" names, served up by Samba, CIFS, or NFS.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-06-27 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 20:05 David DLC
2017-06-27 20:25 ` Nellis, Kenneth
2017-06-27 20:31 ` Jon Turney
2017-06-27 21:42 ` Brian Inglis [this message]
2017-06-27 20:59 David DLC
2017-06-28 17:14 David DLC
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=1adcd353-b759-d423-3612-78b88a1fa7e1@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@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: link
Be 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).