no, actually the
--with-socket-dir option
is working perfectly
I am now trying to find a safe location to chmod 777 (I'm paranoid)
thanks!
2009/3/4 Aaron Davies :
> On Mar 4, 2009, at 6:02 PM, Pau wrote:
>
>> Probably I am not understanding something or I am being obscure. Sorry
>> in any case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> Try adding the line:
>
>> terminfocap screen* ks@:ke@
>
>> to your final destination host's ~/.screenrc or /etc/screenrc, and see
>> if that makes a difference in (freshly started) screen sessions.
>
> I a
Hi,
I have a similar setup in which I rename screen windows according to the
current directory. If the path gets too long (more than 20 chars), I
truncate it, more precisely, I truncate a prefix exactly long enough
such that the resulting string is 18 chars long, then I prepend ".." to
the string
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> The \E[?1 sets "cursor key mode", and the \E= sets "application mode".
>> You may possibly want to keep \E= if it doesn't screw things up, so now
>> try changing the line to:
>
>> termcapinfo screen* ks=\E=:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> Chris Lieb wrote:
>> Micah Cowan wrote:
>>> Try adding the line:
>>> terminfocap screen* ks@:ke@
>>> to your final destination host's ~/.screenrc or /etc/screenrc, and see
>>> if that makes a difference in (freshly started) scree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> Try adding the line:
>
>> terminfocap screen* ks@:ke@
>
>> to your final destination host's ~/.screenrc or /etc/screenrc, and see
>> if that makes a difference in (freshly started) screen sessions.
>
> I a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> Try adding the line:
>
> terminfocap screen* ks@:ke@
>
> to your final destination host's ~/.screenrc or /etc/screenrc, and see
> if that makes a difference in (freshly started) screen sessions.
I added the line:
term
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> Chris Lieb wrote:
>>> I am a new screen user and have run into a problem.
>>> When I ssh into a server, screen automatically starts, just as I want.
>>> The number pad works without issue. I then ssh into anot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Asif Iqbal wrote:
> On Wed, Mar 4, 2009 at 12:49 PM, Micah Cowan wrote:
> Perhaps the easiest way to deal with it (for screen only), is to add the
> following line to your ~/.screenrc or /etc/screenrc:
>
> termcapinfo xterm* kN=\E[6~:kP=\E[5~
>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> Chris Lieb wrote:
>> I am a new screen user and have run into a problem.
>
>> When I ssh into a server, screen automatically starts, just as I want.
>> The number pad works without issue. I then ssh into another server,
>> where
On Wed, Mar 4, 2009 at 12:49 PM, Micah Cowan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Asif Iqbal wrote:
>> On Wed, Mar 4, 2009 at 3:39 AM, Micah Cowan wrote:
>> - What is the output of the "infocmp" command
>>
>>> # Reconstructed via infocmp from file: /usr/share/lib/te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Asif Iqbal wrote:
> On Wed, Mar 4, 2009 at 3:39 AM, Micah Cowan wrote:
> - What is the output of the "infocmp" command
>
>> # Reconstructed via infocmp from file: /usr/share/lib/terminfo/x/xterm
>> xterm|vs100|xterm terminal emulator,
The o
On Mar 4, 2009, at 6:02 PM, Pau wrote:
Probably I am not understanding something or I am being obscure. Sorry
in any case.
I would like my session to be saved even after a boot.
this is out of scope for screen, at least if you expect anything other
than your layout to be saved. you may wan
Probably I am not understanding something or I am being obscure. Sorry
in any case.
I would like my session to be saved even after a boot.
Is there a way to do that? I am not native in English and, even though
I spent an amount of time looking for the information, probably I was
not looking for t
On Wed, Mar 4, 2009 at 3:39 AM, Micah Cowan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Asif Iqbal wrote:
>> Hi
>>
>> from my screen window I tried to bind the pgup key to scrollback like this
>>
>> :bindkey -k kP copy
>>
>> After that I hit `pgup' button and I get a `~' instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> Pau wrote:
>> Hello,
>
>> I was wondering whether it is possible to change the location of
>> uscreens from /tmp to some other place, because it gets deleted
>> everytime the computer boots, which it does, because it is a laptop.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Asif Iqbal wrote:
> Hi
>
> from my screen window I tried to bind the pgup key to scrollback like this
>
> :bindkey -k kP copy
>
> After that I hit `pgup' button and I get a `~' instead of expected
> scollback behavior.
Most likely the terminfo/te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pau wrote:
> Hello,
>
> I was wondering whether it is possible to change the location of
> uscreens from /tmp to some other place, because it gets deleted
> everytime the computer boots, which it does, because it is a laptop.
> It would be very useful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> I am a new screen user and have run into a problem.
>
> When I ssh into a server, screen automatically starts, just as I want.
> The number pad works without issue. I then ssh into another server,
> where screen also automatically
19 matches
Mail list logo
