On Thu, 6 May 2021 18:12:38 +0900
Takashi Yano via Cygwin> wrote:
> On Wed, 5 May 2021 15:07:04 +0200 (CEST)
> Johannes Schindelin wrote:
> > Hi,
> >
> > On Fri, 30 Apr 2021, Kevin Locke wrote:
> >
> > > On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> > > > On Fri, 30 Apr 2021 08:25:12 -
On Wed, 5 May 2021 15:07:04 +0200 (CEST)
Johannes Schindelin wrote:
> Hi,
>
> On Fri, 30 Apr 2021, Kevin Locke wrote:
>
> > On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> > > On Fri, 30 Apr 2021 08:25:12 -0600 Kevin Locke wrote:
> > >> I'm investigating an issue in Git for Windows[^1],
Hi,
On Fri, 30 Apr 2021, Kevin Locke wrote:
> On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> > On Fri, 30 Apr 2021 08:25:12 -0600 Kevin Locke wrote:
> >> I'm investigating an issue in Git for Windows[^1], which also affects
> >> Cygwin. The issue is that, when using CMD (i.e. Command P
On Fri, Apr 30, 2021 at 1:31 PM Takashi Yano via Cygwin
wrote:
> Why on earth do you want to set TERM=cygwin?
> If you don't set TERM=cygwin, TERM is automatically set to
> xterm-256color, in which the issue does not occur.
>
Might be because for the longest time, if you didn't set it to cygwin,
On Fri, 30 Apr 2021 10:40:33 -0600
Brian Inglis wrote:
> On 2021-04-30 08:53, Takashi Yano via Cygwin wrote:
> > On Fri, 30 Apr 2021 08:25:12 -0600
> > Kevin Locke wrote:
> >> Hi All,
> >>
> >> I'm investigating an issue in Git for Windows[^1], which also affects
> >> Cygwin. The issue is that, wh
On 2021-04-30 08:53, Takashi Yano via Cygwin wrote:
On Fri, 30 Apr 2021 08:25:12 -0600
Kevin Locke wrote:
Hi All,
I'm investigating an issue in Git for Windows[^1], which also affects
Cygwin. The issue is that, when using CMD (i.e. Command Prompt) on
Windows 10 1703 or above with "Legacy Conso
On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> On Fri, 30 Apr 2021 08:25:12 -0600 Kevin Locke wrote:
>> I'm investigating an issue in Git for Windows[^1], which also affects
>> Cygwin. The issue is that, when using CMD (i.e. Command Prompt) on
>> Windows 10 1703 or above with "Legacy Con
On Fri, 30 Apr 2021 08:25:12 -0600
Kevin Locke wrote:
> Hi All,
>
> I'm investigating an issue in Git for Windows[^1], which also affects
> Cygwin. The issue is that, when using CMD (i.e. Command Prompt) on
> Windows 10 1703 or above with "Legacy Console Mode"[^2] disabled, if
> TERM=cygwin is se
> By the way, the update also fixed a problem I was having (which was
> why I wanted to RTFM): In the previous release (on x86, at least), the
> info and window list output ("C-a i" and "C-a w" respectively) would
> appear at the bottom of my mintty window, rather than in the title
> bar. With 4.2.
Andrew and Achim,
Thanks for the quick turnaround. I just downloaded the new release
(4.2.1-3) and the man pages and info docs are there.
By the way, the update also fixed a problem I was having (which was
why I wanted to RTFM): In the previous release (on x86, at least), the
info and window list
> David Eisner gmail.com> writes:
> > Is this intentional, or am I missing something? Thanks.
>
> Looks like a packaging error for x86 (the x86_64 package is OK).
Hm, sure enough. Sorry about that. Not sure what went wrong, but I'll get
a new release out with the documentation. Andrew
--
Pr
David Eisner gmail.com> writes:
> Is this intentional, or am I missing something? Thanks.
Looks like a packaging error for x86 (the x86_64 package is OK).
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
> In any case, I've tested the patch below, and it solves the immediate
> problem with screen. It probably needs to go upstream too... I'd put
> my hand up, but I'm unsure where upstream is exactly.
I've uploaded a new test release of screen that incorporates this patch. So
we'll see if it fixes t
On May 15 22:54, Shaddy Baddah wrote:
> Hi Corinna,
>
>
> On 2014-05-15 17:17+1000, Corinna Vinschen wrote:
> >
> >
> >Nice detective work, really. The goldstar is well deservered :)
> >
> >On May 15 04:00, Shaddy Baddah wrote:
> >>I quickly worked out that the code has a bug for "%i". At some p
Hi Corinna,
On 2014-05-15 17:17+1000, Corinna Vinschen wrote:
Nice detective work, really. The goldstar is well deservered :)
On May 15 04:00, Shaddy Baddah wrote:
I quickly worked out that the code has a bug for "%i". At some point
the code was changed to push and pop the parameters being
Hi,
On 2014-05-15 04:15+1000, Andrew Schulman wrote:
I can't understand why the ./conftest.exe differ. Trying to emulate by
hand, I cannot reproduce it. But it is now very late here, and I can't
debug anymore.
I'm hoping that I've provided enough of a lead for someone of authority
to decid
Nice detective work, really. The goldstar is well deservered :)
On May 15 04:00, Shaddy Baddah wrote:
> I quickly worked out that the code has a bug for "%i". At some point
> the code was changed to push and pop the parameters being passed (0 and
> 39 in my eg.). However, the "%i" select/case b
> >> I'm hoping that I've provided enough of a lead for someone of authority
> >> to decide where things are right, and where things are wrong.
> >
> >Yes, I think so!
> >
> >Thanks a lot, Shaddy. That takes us a long way to a solution. I'll look
> >at it from there as soon as I can.
>
> Andrew
On Wed, May 14, 2014 at 02:15:38PM -0400, Andrew Schulman wrote:
>
>
>> The 32-bit defines TERMINFO:
>>
>> config.h:
>>
>> /*
>> * Define TERMINFO if your machine emulates the termcap routines
>> * with the terminfo database.
>> * Thus the .screenrc file is parsed for
>> * the command 'te
> The 32-bit defines TERMINFO:
>
> config.h:
>
> /*
> * Define TERMINFO if your machine emulates the termcap routines
> * with the terminfo database.
> * Thus the .screenrc file is parsed for
> * the command 'terminfo' and not 'termcap'.
> */
> #define TERMINFO 1
>
> configure.log:
>
H,
On 2014-05-15 02:46+0100, Andrew Schulman wrote:
The problem only occurs with screen on 64-bit Cygwin. The 32-bit appears
to work correctly. The problem is that when screen is run in mintty, it
seems to exclude the bottom line, reducing the actual size of the
buffer. Further, something goes
Hi Shaddy.
> Hi,
>
> This is a problem that I noticed some time last year, so I apologise for
> sitting on it for so long. I actually started drafting a number of
> emails to report but never committed.
>
> The problem only occurs with screen on 64-bit Cygwin. The 32-bit appears
> to work correc
On May 13 00:57, Shaddy Baddah wrote:
> Hi,
>
> This is a problem that I noticed some time last year, so I apologise for
> sitting on it for so long. I actually started drafting a number of
> emails to report but never committed.
>
> The problem only occurs with screen on 64-bit Cygwin. The 32-bi
On Sat, May 03, 2014 at 07:52:22PM +, Dawid Ferenczy wrote:
>Christopher Faylor cygwin.com> writes:
>
>> I duplicated this. The command window that I use doesn't exhibit this
>> behavior. I thought I'd tested pure cmd when making the recent spate of
>> console handling changes but this one m
Christopher Faylor cygwin.com> writes:
> I duplicated this. The command window that I use doesn't exhibit this
> behavior. I thought I'd tested pure cmd when making the recent spate of
> console handling changes but this one must have slipped by.
>
> It's a shame that, when I repeatedly asked
On Fri, May 2, 2014 at 7:37 AM, Christopher Faylor wrote:
(snip)>
> Oh, and another reason for my reaction was that the web page used the
> term "annoying cygwin behavior" when Cygwin is working as designed.
One man's "working as designed" is another man's "annoying behavior" :)
Csaba
--
GCS a+
Christopher Faylor cygwin.com> writes:
>
> On Fri, May 02, 2014 at 01:33:30AM -0400, Christopher Faylor wrote:
> >I think I understand now. The request if for Cygwin to "do nothing"
> >when it sees escape sequences since, apparently, ConEmu will handle
> >escape sequences on its own. This is n
On Fri, May 02, 2014 at 01:33:30AM -0400, Christopher Faylor wrote:
>I think I understand now. The request if for Cygwin to "do nothing"
>when it sees escape sequences since, apparently, ConEmu will handle
>escape sequences on its own. This is not a bug in Cygwin but, a request
>for different fun
On Thu, May 01, 2014 at 06:10:25PM -0400, Larry Hall (Cygwin) wrote:
>On 05/01/2014 06:13 AM, Maximus5 wrote:
>> Christopher Faylor cygwin.com> writes:
>>
>>> I don't see the behavior that you are specifying but I doubt that what
>>> you are seeing has anything to do with the gobbledegook on the a
On 05/01/2014 06:13 AM, Maximus5 wrote:
Christopher Faylor cygwin.com> writes:
I don't see the behavior that you are specifying but I doubt that what
you are seeing has anything to do with the gobbledegook on the above
page. If you do want "Cygwin" to send ANSI escape sequences then you'll
ne
Christopher Faylor cygwin.com> writes:
> I don't see the behavior that you are specifying but I doubt that what
> you are seeing has anything to do with the gobbledegook on the above
> page. If you do want "Cygwin" to send ANSI escape sequences then you'll
> need to make sure that you're using a
Hi David Ferenczy,
>> I'm still having issues with applications which use alternative screen
>> for output (LESS, MAN). When I exit that application, its output stays
>> on screen, prompt is displayed over it.
>
> [snip]
>
>> Example steps to reproduce the issue:
>>
>> 1. execute "man grep"
>> 2.
On Sat, Apr 26, 2014 at 08:16:00PM +, Dawid Ferenczy wrote:
>Christopher Faylor cygwin.com> writes:
>
>> Perhaps you aren't a native English speaker and incorrectly took offense
>> at the mild term "gobbledegook" which was not directed at you. I was
>> referring to the author of the web page
Christopher Faylor cygwin.com> writes:
> Perhaps you aren't a native English speaker and incorrectly took offense
> at the mild term "gobbledegook" which was not directed at you. I was
> referring to the author of the web page that you referenced. If that is
> the author of ConEmu then he reall
Christopher Faylor cygwin.com> writes:
> Anyway, this should be fixed in the latest snapshot:
>
> http://cygwin.com/snapshots/
>
> cgf
Nice! It works fine now. Thank you very much for that, because it was really
pain for me. I appreciate that.
Have a nice day.
--
David Ferenczy
http://tw
Christopher Faylor cygwin.com> writes:
> I duplicated this. The command window that I use doesn't exhibit this
> behavior. I thought I'd tested pure cmd when making the recent spate of
> console handling changes but this one must have slipped by.
>
> It's a shame that, when I repeatedly asked
On Sat, Apr 26, 2014 at 06:21:55PM +, Dawid Ferenczy wrote:
>Christopher Faylor cygwin.com> writes:
>
>> "doesn't send ANSI codes to the console" doesn't make a lot of sense.
>> "Cygwin" doesn't send ANSI codes to the windows console since the windows
>> console doesn't understand ANSI codes.
Christopher Faylor cygwin.com> writes:
> "doesn't send ANSI codes to the console" doesn't make a lot of sense.
> "Cygwin" doesn't send ANSI codes to the windows console since the windows
> console doesn't understand ANSI codes.
I didn't know that. So how does it work, that I'm able to set cmd.ex
Christopher Faylor cygwin.com> writes:
> "doesn't send ANSI codes to the console" doesn't make a lot of sense.
> "Cygwin" doesn't send ANSI codes to the windows console since the windows
> console doesn't understand ANSI codes.
>
> I don't see the behavior that you are specifying but I doubt tha
On Fri, Apr 25, 2014 at 01:36:17PM -0400, Christopher Faylor wrote:
>I don't see the behavior that you are specifying...
I duplicated this. The command window that I use doesn't exhibit this
behavior. I thought I'd tested pure cmd when making the recent spate of
console handling changes but this
> I'm still having issues with applications which use alternative screen for
> output (LESS, MAN). When I exit that application, its output stays on
> screen, prompt is displayed over it.
>
> My system is as follows:
>
[snip]
> Example steps to reproduce the issue:
>
> 1. execute "man grep"
> 2. s
On Fri, Apr 25, 2014 at 05:20:21PM +, Dawid Ferenczy wrote:
>Hi,
>
>I'm still having issues with applications which use alternative screen for
>output (LESS, MAN). When I exit that application, its output stays on
>screen, prompt is displayed over it.
>
>My system is as follows:
>
>OS: Window
> Hello,
>
> When 'screen' is running in a mintty window and I resize it, screen
> understandably uses the old window geometry. Is there a way to tell
> screen to update its geometry? I've searched for this many times but
> 'screen' is too generic to narrow down the result set (I get a lot of
> mo
Terris Linenbach wrote:
> When 'screen' is running in a mintty window and I resize it, screen
> understandably uses the old window geometry. Is there a way to tell
> screen to update its geometry?
This isn't a Cygwin question, it's a question about screen generally. You'd be
better off asking on
On 2/5/2012 12:45 AM, Ilya Dogolazky wrote:
> STEPS LEADING TO PROBLEM:
>
> 1. Open a command line window in Windows (the standard one or rxvt: I
> tried both: no difference), then either detach from the session or not
> (I tried both: no difference)
>
> 2. Connect to the Windows machine from a l
On 3/3/2011 1:51 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Rafael Kitover sent the following at Thursday, March 03, 2011 1:29 PM
>> It seems when in screen in the console, native windows programs that use
>> the console don't work correctly.
>
> Not unexpected. See the documentation. The fo
Rafael Kitover sent the following at Thursday, March 03, 2011 1:29 PM
>It seems when in screen in the console, native windows programs that use
>the console don't work correctly.
Not unexpected. See the documentation. The following is a good place to
start. Or search the mailing list.
http://cy
On 10/13/2010 09:29 AM, Eric Blake wrote:
(3) teach upstream screen that it should use getpwent() and honor the
pw_shell entry for the user, rather than relying on $SHELL
(4) Use $SHELL if it is in the environment, otherwise, use getpwent()
and honor pw_shell rather than hard-coding /bin/sh as
On 10/13/2010 09:22 AM, Andrew Schulman wrote:
On 12/10/2010 18:00, Andrew Schulman wrote:
Initially SHELL=/bin/bash when using a link in start menu.From initial bash
prompt, i start screen, fresh session. There all kinds of bash misbehavior
occur, including ~/.bashrc having no effect. Apparen
> On 12/10/2010 18:00, Andrew Schulman wrote:
> >> Initially SHELL=/bin/bash when using a link in start menu.From initial
> >> bash prompt, i start screen, fresh session. There all kinds of bash
> >> misbehavior occur, including ~/.bashrc having no effect. Apparent reason
> >> for that is that $
On 12/10/2010 18:00, Andrew Schulman wrote:
Initially SHELL=/bin/bash when using a link in start menu.From initial bash
prompt, i start screen, fresh session. There all kinds of bash misbehavior
occur, including ~/.bashrc having no effect. Apparent reason for that is that
$SHELL becomes /bin/s
> Initially SHELL=/bin/bash when using a link in start menu.From initial bash
> prompt, i start screen, fresh session. There all kinds of bash misbehavior
> occur, including ~/.bashrc having no effect. Apparent reason for that is that
> $SHELL becomes /bin/sh instead of /bin/bash within screen.
> Yes, I understand that it is not possible for you to invest too much
> time into an exotic bug like this one. Thank you for the response.
It's not exotic... just a bit unusual :) But it is important. I wish I
could solve it, but I can't commit the time to do it.
> Apparently, reattaching wor
Andrew,
Yes, I understand that it is not possible for you to invest too much
time into an exotic bug like this one. Thank you for the response.
Apparently, reattaching works from rxvt if the detached 'screen' process
was launched from the console. With a little bit of luck it let me
continue usin
> I start 'screen -d -m MYCOMMAND' and it goes into background, as
> intended. However, I cannot reattach to it, the reattaching 'screen'
> process hangs. It is easy to reproduce:
>
> sh-3.2# screen -d -m sleep 1000
>
> sh-3.2# screen -ls
> There is a screen on:
> 1072..rock (Detache
> $ diff -U 0 env-*
> --- env-bash.txt2010-01-13 19:58:53.0 -0500
> +++ env-rxvt.txt2010-01-13 19:58:53.0 -0500
> @@ -6 +6 @@
> -TERM=cygwin
> +TERM=rxvt-cygwin-native
I tried changing TERM before with no success. But I did re-try, again
with no success :)
I also
> > I just built a new screen package that uses libncurses10 instead of
> > libncurses9. Please try it out and see if it makes a difference.
> >
> > (1) In setup, make sure that crypt, libgcc1, and libncurses10 are
> > installed.
> >
> > (2) Kill any running screen sessions.
> >
> > (3) Run
> >
> Environment variables?
>
> I just built a new screen package that uses libncurses10 instead of
> libncurses9. Please try it out and see if it makes a difference.
>
> (1) In setup, make sure that crypt, libgcc1, and libncurses10 are
> installed.
>
> (2) Kill any running screen sessions.
>
>
> I have learned one very mystical proceedure. If I launch the bash
> shortcut which just runs bash --login -i, then I launch my rxvt
> shortcut, screen works as it always has for me. Go figure!.
Environment variables?
I just built a new screen package that uses libncurses10 instead of
libnc
> Have you tried to reproduce this problem in a different terminal? Have you
> tried removing your .screenrc?
It does not make a difference using other terminals.
I have learned one very mystical proceedure. If I launch the bash
shortcut which just runs bash --login -i, then I launch my rxvt
s
> Sorry for the resend, forgot to attach the file.
>
> I now have Cygwin installed successfully on an Alienware laptop running
> Windows 7. Its a new install. To get Cygwin installed I had to
> uninstall Bitdefender 2010. I have left it uninstalled. I can start
> rxvt using both the installed
2009/7/5 Sylvain Pasche:
> (by the way, I recently discovered MinTTY and I'm pretty impressed. MinTTY +
> screen offers a very nice multiple-tab environment on Cygwin).
Thanks!
Btw, you can enable browser-style tab switching with (Shift+)Ctrl+Tab
by mapping MinTTY's keycodes for those in .screenr
On 7/5/2009 7:37 PM, Christopher Faylor wrote:
I'd appreciate it if you would test this and let everyone know. You
have the power:
http://cygwin.com/snapshots/
Tried with the 2009-07-04 snapshot, and the issue is gone :-). No more
console windows are opened when launching screen and I didn't
On Sun, Jul 05, 2009 at 06:15:51PM +0200, Sylvain Pasche wrote:
>I saw the recent thread about the unwanted console windows appearing
>with MinTTY on Win7.
>
>I just wanted to mention that I see a similar issue with screen in the
>same environment (Win7 RC 64-bit, Cygwin 1.7, screen 4.0.3-1): Each
> [EMAIL PROTECTED] ~ $ screen -r
> There is no screen to be resumed.
> [EMAIL PROTECTED] ~ $ screen cmd
> [detached]
> [EMAIL PROTECTED] ~ $ screen -r
> [EMAIL PROTECTED] ~ $ screen -mS irc irssi
> [detached]
> [EMAIL PROTECTED] ~ $ screen -r
> There are several suitable screens on:
> 2628
> And so I settled for the self-conclusion
> that this was a 'dead' package, waiting for someone to look at...
No, the package is not dead. Cygwin has the latest release, version 4.0.3, and
I'm not aware of any current problem reports on it.
> So, can you tell me if these hanging problems were
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Julio Emanuel wrote:
| So, can you tell me if these hanging problems were after all fixed,
| and I'm the only one with them? Or is this just a matter of luck,
| because I've now seen some mails of people talking so good of this
| cygwin package...?
Hi!
I have problems reattaching to screen under a ssh session.
I have rebuild screen with debug enabled, run screen under ssh
session, detached and tried to reattach under the same ssh session.
When i tried to attach, the background screen debug log printed:
+ hit ev fd 5 type 1!
Knock - knock!
Damjan Lango wrote:
I'm still having problems with reattaching screen under ssh sessions.
Does it work to anybody at all? ssh + screen + vista anyone?
sigh :(
I have had some success using vista 64 bit. Not frequently used, though.
Jim
--
Unsubscribe info: http://cygwin.com/ml/#unsubscr
As I see you're requesting cygcheck -s -v -r output for other
problems, I'm attaching it here as well if it helps with my ssh /
screen reattach problem.
btw, when cygcheck completed, it also reported:
'id' program not found
'id' program not found
but id is working fine:
$ id
uid=1000(Damjan) gid=51
Another update on my screen adventures, please accept my apologies
since i'm posting so frequently.
I have removed completely the /tmp/uscreens/S-Damjan directory and
it's contents and killed all the cygwin processes. Now screen
reattaching works in CMD cygwin bash window as well (and rxvt and
xte
Correction: besides rxvt, screen also works in xterm.
However I can't get screen working in the default cygwin CMD console
running bash and also can't get it working over ssh.
On 2007-10-05, Damjan Lango wrote:
> I have read the screen/README.Cygwin and couldn't find a solution.
> I have set the
I have tried with an user that is in administrators group and it still
doesn't work.
and the cat socket error really is no such device or address and the
same is reported in rxvt so I guess we can't conclude from that that
permissions are a problem.
What other info can I provide?
Should I strace s
Andrew Schulman wrote:
> Andrew Schulman wrote:
> >> Hi!
> >> What is the current status of screen reattach?
> >> For me it does not work under the default cygwin bash shell, which
> >> uses cmd console afaik and it does not work under cygwin sshd. The
> >> only way it works is under cygwin rxvt. I
Andrew Schulman wrote:
Hi!
What is the current status of screen reattach?
For me it does not work under the default cygwin bash shell, which
uses cmd console afaik and it does not work under cygwin sshd. The
only way it works is under cygwin rxvt. I would most like to use it
under sshd.
What's th
> Hi!
> What is the current status of screen reattach?
> For me it does not work under the default cygwin bash shell, which
> uses cmd console afaik and it does not work under cygwin sshd. The
> only way it works is under cygwin rxvt. I would most like to use it
> under sshd.
> What's the magic to
I tried sshing in over putty and also from a linux gnome-term on a
different machine.
Btw, I'm using Vista, is this a problem perhaps?
Also the user I'm ssh-ing into does not have administrator privleges,
might try changing that. I tried to do a cat
/tmp/uscreens/S-name/socket-name and it says perm
On 2007-10-04, Damjan Lango wrote:
> Hi!
> What is the current status of screen reattach?
> For me it does not work under the default cygwin bash shell, which
> uses cmd console afaik and it does not work under cygwin sshd. The
> only way it works is under cygwin rxvt. I would most like to use it
>
On 2007-10-04, Gary Johnson wrote:
> On 2007-10-04, Damjan Lango wrote:
> > Hi!
> > What is the current status of screen reattach?
> > For me it does not work under the default cygwin bash shell, which
> > uses cmd console afaik and it does not work under cygwin sshd. The
> > only way it works is u
* Andrew Louie (Wed, 25 Jul 2007 08:33:36 -0400)
> On 7/25/07, Thorsten Kampe wrote:
> > Screen will *never ever* source your .bashrc, that's for sure.
>
> except when you source your .bashrc file from .bash_profile, and
> thought it would be a neat trick to call screen from .bashrc so that
> it
On 7/25/07, Thorsten Kampe wrote:
Screen will *never ever* source your .bashrc, that's for sure.
except when you source your .bashrc file from .bash_profile, and
thought it would be a neat trick to call screen from .bashrc so that
it will start up when you start cygwin.
boy, was my face
* yitzle (Wed, 25 Jul 2007 00:17:50 -0400)
> > Then on my Fedora Core system '/etc/screenrc' contains:
> >
> > # make the shell in every window a login shell
> > #shell -$SHELL
> >
> > So maybe look in '/etc/screenrc' and see if there's a similar setting there
> > that you can enable? Otherwise, j
* yitzle (Tue, 24 Jul 2007 23:30:56 -0400)
> Under RedHat/Fedora, when screen starts up, it will execute (source)
> my .bashrc file.
> Under cygwin, it doesn't.
> Bug? Feature request?
Screen will *never ever* source your .bashrc, that's for sure.
Thorsten
--
Unsubscribe info: http://cygwi
Then on my Fedora Core system '/etc/screenrc' contains:
# make the shell in every window a login shell
#shell -$SHELL
So maybe look in '/etc/screenrc' and see if there's a similar setting there
that you can enable? Otherwise, just add it to your '~/.screenrc'.
That line does the trick. Thanks
yitzle wrote:
Under RedHat/Fedora, when screen starts up, it will execute (source)
my .bashrc file.
Under cygwin, it doesn't.
Bug? Feature request?
Disabled feature? I don't know much about screen (never used it myself)
but looking at the man page I find:
shell command
Set the comm
> At 16-2-2007 22:38, Frank Fesevur wrote:
> > I have just tried it and so far it works for me. Although I must admit I
> > have only used it very limited. But a colleague just mailed that he
> > could not detach/retach :-S
>
> This detach/retach problem seems to be caused by an incomplete unins
At 16-2-2007 22:38, Frank Fesevur wrote:
I have just tried it and so far it works for me. Although I must admit I
have only used it very limited. But a colleague just mailed that he
could not detach/retach :-S
This detach/retach problem seems to be caused by an incomplete uninstall
of an olde
On Sun, Feb 18, 2007 at 08:29:41AM -0800, Christopher Layne wrote:
>On Fri, Feb 16, 2007 at 04:14:06PM -0500, Christopher Faylor wrote:
>> On Fri, Feb 16, 2007 at 01:01:23PM -0500, Andrew Schulman wrote:
>> >> And, just in case you're wondering if I am going to volunteer to help you
>> >> track dow
On Fri, Feb 16, 2007 at 04:14:06PM -0500, Christopher Faylor wrote:
> On Fri, Feb 16, 2007 at 01:01:23PM -0500, Andrew Schulman wrote:
> >> And, just in case you're wondering if I am going to volunteer to help you
> >> track down problems - I'm not. So, maybe anyone who wants screen should
> >> vo
* Andrew Schulman (Fri, 16 Feb 2007 13:10:47 -0500)
> > Could you post a link to your latest build (and sources), so people can
> > test and comment on it.
>
> Sure:
>
> http://home.comcast.net/~andrex/cygwin/screen/setup.hint
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.t
At 16-2-2007 19:10, Andrew Schulman wrote:
Could you post a link to your latest build (and sources), so people can
test and comment on it.
Sure:
http://home.comcast.net/~andrex/cygwin/screen/setup.hint
http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.tar.bz2
http://home.comcas
On Fri, Feb 16, 2007 at 01:01:23PM -0500, Andrew Schulman wrote:
>> And, just in case you're wondering if I am going to volunteer to help you
>> track down problems - I'm not. So, maybe anyone who wants screen should
>> volunteer to help.
>
>No, that was not my intention. I was trying to be court
> Could you post a link to your latest build (and sources), so people can
> test and comment on it.
Sure:
http://home.comcast.net/~andrex/cygwin/screen/setup.hint
http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.tar.bz2
http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-
> And, just in case you're wondering if I am going to volunteer to help you
> track down problems - I'm not. So, maybe anyone who wants screen should
> volunteer to help.
No, that was not my intention. I was trying to be courteous. But that's a
two-way street. Forget it, I won't bother next ti
Andrew Schulman wrote:
screen is an extremely useful program, that people have been asking for in
Cygwin for a long time. I'd be willing to package it, but when I floated
the idea a year ago or so, the feeling seemed to be that there were still
too many bugs to make it useful. If people can liv
On Thu, Feb 15, 2007 at 08:16:02PM -0500, Andrew Schulman wrote:
>> >screen is an extremely useful program, that people have been asking for in
>> >Cygwin for a long time. I'd be willing to package it, but when I floated
>> >the idea a year ago or so, the feeling seemed to be that there were still
> >screen is an extremely useful program, that people have been asking for in
> >Cygwin for a long time. I'd be willing to package it, but when I floated
> >the idea a year ago or so, the feeling seemed to be that there were still
> >too many bugs to make it useful. If people can live with (or ev
On Thu, Feb 15, 2007 at 04:27:22PM -0500, Andrew Schulman wrote:
>> Will this have any impact on having a version of screen that works?
>
>I have a working version of screen on Cygwin. I use it daily, and it works
>fine. With CYGWIN=tty set, the reattachment bug appears to be solved; it
>detaches
On Sun, Nov 12, 2006 at 12:38:23PM -0500, Christopher Faylor wrote:
>On Sun, Nov 12, 2006 at 04:30:59PM +, Borg wrote:
>>Okey. I was able to find why ./configure was failing in random places.
>>It was bash fault...
>
>Or it was your fault for not doing your homework on what was new with
>bash.
On Sun, Nov 12, 2006 at 04:30:59PM +, Borg wrote:
>Okey. I was able to find why ./configure was failing in random places.
>It was bash fault...
Or it was your fault for not doing your homework on what was new with
bash. Easier to blame a program, though, eh?
>Problem with cygwin-1.5.21 and P
1 - 100 of 122 matches
Mail list logo
