Re: The HOME variable

2004-07-07 Thread Ken Dibble
I just edited the appropriate fields in /etc/passwd. (first field and 
next to last field)

Ken
George wrote:
Could someone enlighten me as to how to go about changing the defaults?
Ideally, I'd like to be able to change the location of  $HOME 
altogether, but more importantly my $USERNAME contains an unfortunate 
space and is causing me some grief.

Thanks.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


Re: The HOME variable

2004-07-07 Thread George
Ken Dibble wrote:
I just edited the appropriate fields in /etc/passwd. (first field and 
next to last field)

Ken
Thanks.  Now if the changing "Program Files" or "Documents and Settings" 
to something less inane would be so easy.

Cheers.
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


Re: The HOME variable

2004-07-07 Thread Igor Pechtchanski
On Wed, 7 Jul 2004, George wrote:

> Ken Dibble wrote:
>
> > I just edited the appropriate fields in /etc/passwd. (first field and
> > next to last field)
> >
> > Ken
>
> Thanks.  Now if the changing "Program Files" or "Documents and Settings"
> to something less inane would be so easy.

Getting to be off-topic for the Cygwin list, but here's a pointer:

In particular, the first and fourth hits look relevant.

As for "Program Files", as far as I know, the name isn't special in any
way -- you can just rename it (and, of course, move all the programs
already installed there - yuk!), or, better yet, simply don't install
Cygwin under it...  Plus (to get this back on-topic), you can use Cygwin
mounts to hide the spaces in directory names, e.g., on my machine:

$ mount | grep java
c:\Program Files\IBM\Java14 on /usr/contrib/java type user (binmode)

HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: The HOME variable

2004-07-07 Thread George

Getting to be off-topic for the Cygwin list, but here's a pointer:

In particular, the first and fourth hits look relevant.
As for "Program Files", as far as I know, the name isn't special in any
way -- you can just rename it (and, of course, move all the programs
already installed there - yuk!), or, better yet, simply don't install
Cygwin under it...  Plus (to get this back on-topic), you can use Cygwin
mounts to hide the spaces in directory names, e.g., on my machine:
$ mount | grep java
c:\Program Files\IBM\Java14 on /usr/contrib/java type user (binmode)
HTH,
Igor
Thanks for that bit of information.  Off-topic can be serendipitous, 
maybe?  IIRC, I might be able to do this next go-around by installing 
Windows with a more custom set of shell folders.

Have you any experience with the Microsoft 'linkd' utility (or 
SysInternals 'join')?  I stumbled across a brief discussion in the 
Cygwin mailing list archives concerning implementing something similar 
but the idea was voted dead in the water.  Using 'ls' won't display 
reparse points, of course, but what can be an administrative nightmare 
could be mitigated somewhat aliasing 'dir' to 'cmd.exe /C dir' for a 
quick and dirty check, or using 'join' to keep abreast of things if one 
were to use that approach.  I know the NTFS mount drive-to-folder has 
its own set of problems.

I guess my question, if there is one, is to what extent can multiple 
drive letter assignments for partitions, hard disks, network mounts, 
etc. be replaced with something more sane?  Or short of a mount here and 
there and a few symlinks thrown in for good measure, is the idea of 
implementing something more Unix-ish a road to even more frustration?

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


Re: The $HOME variable; rxvt and .inputrc

2006-05-15 Thread Andrew DeFaria

George wrote:

1. Does the admonition against setting $HOME as a Windows 
environmental variable still stand, or was that an old wives' tale?

I have mine set. No problems.
2. I hesitate to ask for a handout, but could some let me know if it's 
possible, and if so how, to assign the SHIFT+PAGEUP and SHIFT+PAGEDOWN 
keystrokes to something more friendly in rxvt? If it's not obvious, 
I'm using 'set -o vi' for bash.
Describe unfriendly. Shift-PageUp and Shift-PageDown effectively page up 
or down through the output buffer. That seems pretty friendly to me...

--
Be different. Conform.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: The $HOME variable; rxvt and .inputrc

2006-05-15 Thread George
On Mon, May 15, 2006 at 07:51:32AM -0700, Andrew DeFaria wrote:
> George wrote:
> 
> >1. Does the admonition against setting $HOME as a Windows 
> >environmental variable still stand, or was that an old wives' tale?

> I have mine set. No problems.

Thanks for that.  I guess I can undo all the inconsistent mucking around 
I've been doing lately.

> >2. I hesitate to ask for a handout, but could some let me know if it's 
> >possible, and if so how, to assign the SHIFT+PAGEUP and SHIFT+PAGEDOWN 
> >keystrokes to something more friendly in rxvt? If it's not obvious, 
> >I'm using 'set -o vi' for bash.

> Describe unfriendly. 

Cough cgf cough.  I keed.  I keed.  How about I describe friendly 
instead?

Friendly is a girl with a nice smile holding my hand and pressing my 
keys for me while serving me rum drinks with little umbrellas in them.

No?

Ok, how about friendly is not having taking my hands off the keyboard's 
home row to reach for PageUp/Down or, worse, the arrow keys?

>Shift-PageUp and Shift-PageDown effectively page up or down through the 
>output buffer. That seems pretty friendly to me...

A key modifier would be in order given that we're talking about a 
textual interface.  Hence, I think CTL+F for forward, and CTL+B for back 
would be more appropriate, if not consistent for a vi user.  Now if it 
was my birthday and I could get what anything I wanted, I'd go for the 
girl with the rum drinks, and opt for CTL+J and CTL+K. 

Regards.

-- 
George


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: The $HOME variable; rxvt and .inputrc

2006-05-15 Thread clayne
On Mon, May 15, 2006 at 11:16:12AM -0700, George wrote:
> Friendly is a girl with a nice smile holding my hand and pressing my 
> keys for me while serving me rum drinks with little umbrellas in them.

See the real issue here is how we can configure rxvt to provide the above.

> No?
> 
> Ok, how about friendly is not having taking my hands off the keyboard's 
> home row to reach for PageUp/Down or, worse, the arrow keys?

Shift-pageup/shift-pagedown are so incredibly embedded into a typical
X/rxvt/xterm users' head at this point that it's pretty much a motor
function. I think that you will find most people using X for the majority
of their work are not sticking to the home keys and proper keyboard position
as a strict order - but only when they need to. It also helps to develop
that 'edge of thumb on top-left of shift + ring finger on page up/down'
action. :) That being said, you *can* change them, but I believe it
requires hacking at your .Xresources file or equivalent.

-cl

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: The $HOME variable; rxvt and .inputrc

2006-05-15 Thread Andrew DeFaria

George wrote:

Describe unfriendly.

Cough cgf cough. I keed. I keed. How about I describe friendly instead?

Friendly is a girl with a nice smile holding my hand and pressing my 
keys for me while serving me rum drinks with little umbrellas in them.


No?

If you figure out how to configure that well then just let me know! :-)
Ok, how about friendly is not having taking my hands off the 
keyboard's home row to reach for PageUp/Down or, worse, the arrow keys?
Hmmm Seems to me like you don't want to configure the PageUp/Down 
keys at all. You probably want something like Shift/Ctrl/Alt/whatever 
"v" or something like that to page up or down. Well sorry but with that 
you are on your own...
Shift-PageUp and Shift-PageDown effectively page up or down through 
the output buffer. That seems pretty friendly to me...
A key modifier would be in order given that we're talking about a 
textual interface. Hence, I think CTL+F for forward, and CTL+B for 
back would be more appropriate, if not consistent for a vi user.
As an Xemacs users I find that highly offensive! ;-) Actually C-f and 
C-b are forward/backward character.


I'm sure there's some way to configure some keystroke to do what you 
want. Look at the rxvt man page perhaps. I haven't taken the time to try 
to figure that out. Honestly there are just too many keystroke 
combinations to remember and to step over if you ask me. And, usually, 
when I feel the need to page backward I'll pipe the output into less or 
just use the mouse or Shift-PageUp/Down keys. It's usually at this time 
that I'm in "reading mode" as opposed to "typing mode" anyways. YMMV.
Now if it was my birthday and I could get what anything I wanted, I'd 
go for the girl with the rum drinks, and opt for CTL+J and CTL+K.

Screw the C-j and C-k - just give me the girl! ;-)
--
Just because I have a short attention span doesn't mean I ... um ... er 
... uh ...



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: The $HOME variable; rxvt and .inputrc

2006-05-16 Thread Lloeki

> Friendly is a girl with a nice smile holding my hand and pressing my
> keys for me while serving me rum drinks with little umbrellas in them.
>

Managed to work this out. Barely.


If you figure out how to configure that well then just let me know! :-)

YMMV too much for a howto. Sorry, you're on your own. Pointers are
switching the task to realtime non preemptable (and others to low and
preemptable), moving the window around regularly (especially revealing
romantic wallpapers, photos of beaches or mountain resorts), and never
ever try emulation (works well at start, but sandboxing leaks in the
end, stopping the whole thing to a grinding halt). Signals
handling/sending is important too. Never SIGHUP, even if she does.
Handle SIGILL gracefully. Always respond to SIGINT. If she send
SIGALRM too much, you might be SIGTSTPped but if handled well, you'll
receive a SIGCONT. You might also be accused of sending rogue SIGSEGV
signals. SIGKILL can occur to you, but you're much likely to receive a
SIGTERM ("let's be friends"). If all goes well you might even SIGPIPE
and eventually she could fork(), and then, pray not to have to handle
SIGCHLD.


Screw the C-j and C-k - just give me the girl! ;-)

It doesn't work too much in the end. Noise on the line, packets get
lost (hey, it's CSMA/CD), so you keys end up not being typed that
often.
Plus you end up receiving lots of priority interrupts and you know,
it's preemptive multitasking, except for one task. And on task
completion, context backswitching doesn't work too well and you end up
messing your work.

Nice cocktails though.

(Now I'll hide that window before my beloved catches me spitting
stupid misogynic jokes like this.)

Lloeki


Re: The $HOME variable; rxvt and .inputrc

2006-05-16 Thread Andrew DeFaria

Lloeki wrote:

> Friendly is a girl with a nice smile holding my hand and pressing my
> keys for me while serving me rum drinks with little umbrellas in them.
>

Managed to work this out. Barely.


Barely!?! Got pics? ;-)


If you figure out how to configure that well then just let me know! :-)
YMMV too much for a howto. Sorry, you're on your own. Pointers are 
switching the task to realtime non preemptable (and others to low and 
preemptable), moving the window around regularly (especially revealing 
romantic wallpapers, photos of beaches or mountain resorts), and never 
ever try emulation (works well at start, but sandboxing leaks in the 
end, stopping the whole thing to a grinding halt). Signals 
handling/sending is important too. Never SIGHUP, even if she does. 
Handle SIGILL gracefully. Always respond to SIGINT. If she send 
SIGALRM too much, you might be SIGTSTPped but if handled well, you'll 
receive a SIGCONT. You might also be accused of sending rogue SIGSEGV 
signals. SIGKILL can occur to you, but you're much likely to receive a 
SIGTERM ("let's be friends"). If all goes well you might even SIGPIPE 
and eventually she could fork(), and then, pray not to have to handle 
SIGCHLD.
I tried that once (actually twice). Now they have off the shelf software 
to handle all of this. Read all about it. 
http://defaria.com/Jokes/TheEvolutionOfSocialSoftware.php


Personally I opted for the Divorce 2.0 solution. Well worth the money...

Screw the C-j and C-k - just give me the girl! ;-)
It doesn't work too much in the end. Noise on the line, packets get 
lost (hey, it's CSMA/CD), so you keys end up not being typed that 
often. Plus you end up receiving lots of priority interrupts and you 
know, it's preemptive multitasking, except for one task. And on task
completion, context backswitching doesn't work too well and you end up 
messing your work.


Nice cocktails though.

(Now I'll hide that window before my beloved catches me spitting 
stupid misogynic jokes like this.)
Fortunately for me I don't have to worry about such things anymore. I'm 
free to be who I naturally am...

--
Love is like war: easy to begin but very hard to stop. - H. L. Mencken


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: The $HOME variable; rxvt and .inputrc

2006-05-17 Thread Joe Smith


"George" wrote in message news:[EMAIL PROTECTED]

1.  Does the admonition against setting $HOME as a Windows environmental
variable still stand, or was that an old wives' tale?

If $HOME is set it windows then it MUST be a windows path, or you can break
other (non-cygwin) programs that respect $HOME. Other than that
setting $HOME is fine, as cygwin will convert the variable to a unix style 
path. 




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/