ot;
|| >returns a message saying that there is no space on the drive,
|| >which is something that "# df -h" deny:
Ciao.
Vincent.
--
Vincent Zweije| "If you're flamed in a group you
<http://www.xs4all.nl/~zweije/> | don't read, does anybody get bu
setting. I could be wrong, of course.
Vincent.
--
Vincent Zweije| "If you're flamed in a group you
<http://www.xs4all.nl/~zweije/> | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r.
signatur
is clearer:
And now I see that there's actually not even about the same resource! #1
and #4 are about resource instance "color1", #2 and #3 are about resource
instance "color".
Oh well, I guess you see things work.
Vincent.
--
Vincent Zweije| "If you'r
a feel about what
classes and instances mean.
By the way, the class for xterm is called XTerm, not Xterm.
Vincent.
--
Vincent Zweije| "If you're flamed in a group you
<http://www.xs4all.nl/~zweije/> | don't read, does anybody get burnt?"
[Xhost should be t
eing used. Alternatively, pass application class
and instance name to appres, for example:
appres XTerm xterm
Vincent.
--
Vincent Zweije| "If you're flamed in a group you
<http://www.xs4all.nl/~zweije/> | don't read, does anybody get burnt?"
[Xhost should be t
a0
|| *color4:#56c2d6
|| *color10: #b6e354
|| *color5:#8c54fe
|| *color11: #feed6c
|| *color6:#465457
|| *color12: #8cedff
|| *color7:#c6
|| *color13: #9e6ffe
Are those the default settings, or did you run xrdb -load already?
Vincen
ity ones, thus letting your settings take effect.
Use the appres tool to find out what the actual settings are that are
loaded in your X server. If this confirms the theory, you can start
finding out where the higher priority settings come from.
Vincent.
--
Vincent Zweije| "If you'
arget; }
In your scripts, the } is probably on a new line: the newline before it
then terminates the command:
cpST(){
cp Source Target # <- newline terminates command
}
Vincent.
--
Vincent Zweije| "If you're flamed in a group you
<http://www.xs4all.nl/~zwei
le quotes. It turns out that without double quotes, the shell first
expands the variable, then expands the filename pattern (which is a
single asterisk). The double quotes prevent filename expansion.
|| salt '*'
|| works fine
Yes. The single quotes prevent filename expansion, but ge
h those quotes) but not the extra
quotes and backslashes set -x prints for you.
|| How can I avoid that?
Depends on how you did it now, of course. Is dialog quoting the entered
value? If so, look there.
Vincent.
--
Vincent Zweije| "If you're flamed in a group you
<http:/
In message <[EMAIL PROTECTED]>, MJ Watson
<[EMAIL PROTECTED]> wrote:
|| After installing 2.0 clean onto my PC, attempts to start up any
|| window manager fails, as does just trying to start an xterm.
||
|| This output is from an attempt to start up fvwm2:
What are you trying to do? Are you tr
In article <[EMAIL PROTECTED]>, Kevin Traas
<[EMAIL PROTECTED]> wrote:
|| Although things work, I do have some strange messages appearing in
|| /var/log/messages. Although things seem to be working okay, I think
|| they're probably something that should be looked into. Can you "shed any
|| l
12 matches
Mail list logo
