Chris Sutcliffe | 1 May 05:25 2010
Picon

Minor patch to /etc/profile

The PS1 definition for ksh in /etc/profile uses the literal ascii
characters '^[' for the escape sequence as opposed to the single byte
escape control code.  The attached patch corrects that as well as
HOSTNAME not being set correctly (at least for mksh).

Finally, would it be appropriate to extend the 'ksh' case to catch
both pdksh as well as mksh?  Basically the case would be:

*ksh*     | -*ksh*     | */*ksh* | \
*ksh*.exe | -*ksh*.exe | */*ksh*.exe )

Chris

--

-- 
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
Attachment (profile.diff): application/octet-stream, 693 bytes
The PS1 definition for ksh in /etc/profile uses the literal ascii
characters '^[' for the escape sequence as opposed to the single byte
escape control code.  The attached patch corrects that as well as
HOSTNAME not being set correctly (at least for mksh).

Finally, would it be appropriate to extend the 'ksh' case to catch
both pdksh as well as mksh?  Basically the case would be:

*ksh*     | -*ksh*     | */*ksh* | \
*ksh*.exe | -*ksh*.exe | */*ksh*.exe )
(Continue reading)

Vincent Pelletier | 1 May 07:50 2010
Picon

1.7.5: sshd environment variables

Hi.

I've just installed cygwin on winxp, for some wine comparative testing.
To make it easier for me, I installed ssh package and started sshd service so 
I could do as much as possible from my main Linux box.

But I noticed the following difference:
- on a windows cygwin term:
  $ cmd /c echo "%ProgramFiles%"
  C:\Program Files
- on an ssh session:
  $ cmd /c echo "%ProgramFiles%"
  %ProgramFiles%
which breaks the script[1] I'm testing.

Is it a bug ?
If not, how can I make ssh session get the same environment variables as a 
"regular" (ie, not remote) cygwin terminal ?

[1] http://code.google.com/p/winezeug/source/browse/trunk/wisotool

Regards,
--

-- 
Vincent Pelletier

John Morrison | 1 May 08:32 2010
Picon

Re: Minor patch to /etc/profile

Hi Chris,

I'm anticipating to have several hours to do these (and other) changes in
the next week or so.

Regards,

John.

On Sat, May 1, 2010 4:25 am, Chris Sutcliffe wrote:
> The PS1 definition for ksh in /etc/profile uses the literal ascii
> characters '^[' for the escape sequence as opposed to the single byte
> escape control code.  The attached patch corrects that as well as
> HOSTNAME not being set correctly (at least for mksh).
>
> Finally, would it be appropriate to extend the 'ksh' case to catch
> both pdksh as well as mksh?  Basically the case would be:
>
> *ksh*     | -*ksh*     | */*ksh* | \
> *ksh*.exe | -*ksh*.exe | */*ksh*.exe )
>
> Chris
>
> --
> Chris Sutcliffe
> http://emergedesktop.org
> http://www.google.com/profiles/ir0nh34d
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
(Continue reading)

Andrey Repin | 1 May 08:56 2010
Picon

Re: How to uninstall Cygwin/X (only)

Greetings, Dave Korn!

>> But the thing is, I'm not sure that just adding a drop-down is a useful
>> thing to do.  

>   Well, I am.  The problem described by the title of the this thread is that
> you can't uninstall a bunch of stuff easily, because as you click your way
> through the spinner you hit various versions on the way to "uninstall" that
> cause dependencies to be selected.  If you can go directly to "uninstall"
> without cycling through all the intermediate settings, the problem is
> trivially solved.

I'm a bit late to the discussion... My problem is exactly as of the OP, I
can't uninstall X components, they keep eachother enabled.

I just have to ask, why don't take already researched and well-working deb/rpm
approach? Could as well steal code from SynAptic (f.e.) for the most part.

But at least right-click would be nice to have, with a short textual
explanation telling user to "Right-click a node to choose action on a
package/group".

--
WBR,
 Andrey Repin (anrdaemon <at> freemail.ru) 01.05.2010, <10:51>

Sorry for my terrible english...

Andrey Repin | 1 May 09:40 2010
Picon

"Error opening terminal: cygwin." when attempting to start lynx

Greetings, All!

As subject line said, I'm receiving this error message when trying to start
lynx browser:

[C:\]$lynx
Error opening terminal: cygwin.

[C:\]$

So, the question is... what gives?

--

-- 
WBR,
 Andrey Repin (anrdaemon <at> freemail.ru) 01.05.2010, <11:23>

Sorry for my terrible english...

d.sastre.medina | 1 May 10:08 2010
Picon

Re: "Error opening terminal: cygwin." when attempting to start lynx

On Sat, May 01, 2010 at 11:40:01AM +0400, Andrey Repin wrote:
> I'm receiving this error message when trying to start
> lynx browser:
> 
> [C:\]$lynx
> Error opening terminal: cygwin.

Hello,

What does `echo $TERM' tells you? (I'm guessing TERM=cygwin)
Does `export TERM=xterm' solve the problem?
Note that it works for me whatever TERM is: cygwin, xterm, screen...
I can only force to fail if I set TERM to nonsense `TERM=sjdfjsfjsf'

(What I don't know is why TERM=cygwin fails for you)

Regards.

--

-- 
Huella de clave primaria: 0FDA C36F F110 54F4 D42B  D0EB 617D 396C 448B 31EB
Christopher Faylor | 1 May 18:08 2010

Re: "Error opening terminal: cygwin." when attempting to start lynx

On Sat, May 01, 2010 at 10:08:21AM +0200, d.sastre.medina <at> gmail.com wrote:
>On Sat, May 01, 2010 at 11:40:01AM +0400, Andrey Repin wrote:
>> I'm receiving this error message when trying to start
>> lynx browser:
>> 
>> [C:\]$lynx
>> Error opening terminal: cygwin.
>
>Hello,
>
>What does `echo $TERM' tells you? (I'm guessing TERM=cygwin)
>Does `export TERM=xterm' solve the problem?
>Note that it works for me whatever TERM is: cygwin, xterm, screen...
>I can only force to fail if I set TERM to nonsense `TERM=sjdfjsfjsf'
>
>(What I don't know is why TERM=cygwin fails for you)

At this point we normally ask for someone to read:

http://cygwin.com/problems.html

and provide the type of information suggested there.

Jim Eberle | 1 May 18:37 2010

File extension for the copy of python2.5.exe

Part of the latest python rollout involved converting the "python" symlink 
into a full file copy. I was wondering if this could be renamed to 
"python.exe".

Without the ".exe" extension, doing a CreateProcess() on "python" fails even 
if the python file exists and is in the calling process' %PATH%.

Likewise, running "python" from a CMD shell (some people do this) fails for 
the same reason.

I don't think this would break things on the Cygwin side -- witness 
"ls.exe".

Thanks,
Jim

Andrey Repin | 1 May 18:39 2010
Picon

Re: "Error opening terminal: cygwin." when attempting to start lynx

Greetings, Christopher Faylor!

>>> I'm receiving this error message when trying to start
>>> lynx browser:
>>> 
>>> [C:\]$lynx
>>> Error opening terminal: cygwin.
>>
>>Hello,
>>
>>What does `echo $TERM' tells you? (I'm guessing TERM=cygwin)
>>Does `export TERM=xterm' solve the problem?
>>Note that it works for me whatever TERM is: cygwin, xterm, screen...
>>I can only force to fail if I set TERM to nonsense `TERM=sjdfjsfjsf'
>>
>>(What I don't know is why TERM=cygwin fails for you)

> At this point we normally ask for someone to read:

> http://cygwin.com/problems.html

> and provide the type of information suggested there.

Though it's apparent that I've just launched lynx as normal application, as
I've always did in the past.
TERM show nothing, this variable is undefined in common Windows environment.

May I ask you what cygcheck mean when listing Far FTP plugin host definitions?
I've left it included, as it contains no private data, but it shouldn't be there.

(Continue reading)

Christopher Faylor | 1 May 18:53 2010

Re: "Error opening terminal: cygwin." when attempting to start lynx

On Sat, May 01, 2010 at 08:39:18PM +0400, Andrey Repin wrote:
>Greetings, Christopher Faylor!
>
>>>> I'm receiving this error message when trying to start
>>>> lynx browser:
>>>> 
>>>> [C:\]$lynx
>>>> Error opening terminal: cygwin.
>>>
>>>Hello,
>>>
>>>What does `echo $TERM' tells you? (I'm guessing TERM=cygwin)
>>>Does `export TERM=xterm' solve the problem?
>>>Note that it works for me whatever TERM is: cygwin, xterm, screen...
>>>I can only force to fail if I set TERM to nonsense `TERM=sjdfjsfjsf'
>>>
>>>(What I don't know is why TERM=cygwin fails for you)
>
>> At this point we normally ask for someone to read:
>
>> http://cygwin.com/problems.html
>
>> and provide the type of information suggested there.
>
>Though it's apparent that I've just launched lynx as normal application, as
>I've always did in the past.
>TERM show nothing, this variable is undefined in common Windows environment.
>
>May I ask you what cygcheck mean when listing Far FTP plugin host definitions?
>I've left it included, as it contains no private data, but it shouldn't be there.
(Continue reading)


Gmane