* Peder Stray had this to say on [12 Feb 2010, 22:48:23 +0100]:
> On Fri, 12 Feb 2010, Sadrul Habib Chowdhury wrote:
>
>> * Peder Stray had this to say on [03 Feb 2010, 20:22:54 +0100]:
>> [snip]
>>>
>>> btw... does the git-screen have support for using the session-name
>>> for sourcing different
On Fri, 12 Feb 2010, Sadrul Habib Chowdhury wrote:
* Peder Stray had this to say on [03 Feb 2010, 20:22:54 +0100]:
[snip]
btw... does the git-screen have support for using the session-name for
sourcing different configs? like 'source .screenrc-$SESSIONNAME' or
some such?
I don't think tha
* Peder Stray had this to say on [03 Feb 2010, 20:22:54 +0100]:
[snip]
>
> btw... does the git-screen have support for using the session-name for
> sourcing different configs? like 'source .screenrc-$SESSIONNAME' or some
> such?
I don't think that's possible. When you are specifying the sessio
On Tue, 2 Feb 2010, Peder Stray wrote:
On Tue, 2 Feb 2010, Sadrul Habib Chowdhury wrote:
* Peder Stray had this to say on [02 Feb 2010, 19:25:29 +0100]:
Why does then 'at' command need a display?
It doesn't anymore! See:
http://git.savannah.gnu.org/gitweb/?p=screen.git;a=commit;h=4b778782
On Tue, 2 Feb 2010, Sadrul Habib Chowdhury wrote:
* Peder Stray had this to say on [02 Feb 2010, 19:25:29 +0100]:
Why does then 'at' command need a display?
It doesn't anymore! See:
http://git.savannah.gnu.org/gitweb/?p=screen.git;a=commit;h=4b778782ce398747f080b7b7ffd8a2e26c3b0a88
Goodie
* Peder Stray had this to say on [02 Feb 2010, 19:25:29 +0100]:
>
> Why does then 'at' command need a display?
It doesn't anymore! See:
http://git.savannah.gnu.org/gitweb/?p=screen.git;a=commit;h=4b778782ce398747f080b7b7ffd8a2e26c3b0a88
Cheers,
Sadrul
_
Why does then 'at' command need a display? I have a screen I sometimes
start with -d -m. In the config file it uses there are a few
'at'-commands that doesn't run when stated in that way. I know the at
command may need a display in som invocations, but not when the first
parameter is a num
