implementing popup windows without a widget set will lead to
a lot of code bloat! (plus it's a lot of work).
You have the following options though: Escape sequence (or
use the settitle.c / mrxvtset.pl programs), your own
keyboard macro (using Esc).
In future versions there might be a workable alternative
though: We should be able to write an external program using
a widget set that does this configuration, and sends the
data back to mrxvt. This should give the features you need,
while keeping mrxvt light :).
GI
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
And for my own, I am not fond of pop-ups. It "can" be not too much annoying sometimes... but I have never seen a case where it was "better" than another way of doing, inside the same windows.
As for mrxvt, which is multi-tab, so really multi-task, in particular, I don't think adding pop-ups is good. If it foreces its way to the foreground, then you would not be able to do stuffs on other tabs and coming back later. If it could go on background, you would forget it and don't know why a tab does not work anymore.
Yet another solution, close to this pop-up idea, is to include a dialog "inside" the tab. Of course this means some "design" decision must be done about how to differentiate a text coming from the child program (the shell), and a text related to mrxvt (tab name changing here for instance), but this can be an interesting alternative...
Jehan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=862337
implementing popup windows without a widget set will lead to
a lot of code bloat! (plus it's a lot of work).
You have the following options though: Escape sequence (or
use the settitle.c / mrxvtset.pl programs), your own
keyboard macro (using Esc).
In future versions there might be a workable alternative
though: We should be able to write an external program using
a widget set that does this configuration, and sends the
data back to mrxvt. This should give the features you need,
while keeping mrxvt light :).
GI
Logged In: NO
And for my own, I am not fond of pop-ups. It "can" be not too much annoying sometimes... but I have never seen a case where it was "better" than another way of doing, inside the same windows.
As for mrxvt, which is multi-tab, so really multi-task, in particular, I don't think adding pop-ups is good. If it foreces its way to the foreground, then you would not be able to do stuffs on other tabs and coming back later. If it could go on background, you would forget it and don't know why a tab does not work anymore.
Yet another solution, close to this pop-up idea, is to include a dialog "inside" the tab. Of course this means some "design" decision must be done about how to differentiate a text coming from the child program (the shell), and a text related to mrxvt (tab name changing here for instance), but this can be an interesting alternative...
Jehan