On 2014-04-16 05:19 -0300, Amadeus Folego wrote:
> I am using tmux just for the scrollback and paste capabilities
There's a patch for scrollback for st at [1]. Maybe you can try that as
well as alternative.
[1] https://groups.google.com/forum/#!topic/wmii/q1KNvhpiheI
--
Balazs
Thanks for the detailed explanation random! I guess I did not use the
correct terms appropriatelly.
Would a suckless library for handling detaching, scrolling and
multiplexing be something that could have some demand and even be used?
Maybe that would make adding functionality to st trivial with
On Wed, Apr 16, 2014, at 4:19, Amadeus Folego wrote:
> It works! As I am using tmux just for the scrollback and paste
> capabilities I am not worried with losing sessions.
>
> Maybe I'll write a suckless multiplexer for this sometime.
Eh - "multiplexing" refers to the multiple session capability,
On Wed, Apr 16, 2014 at 10:19 AM, Amadeus Folego
wrote:
> It works! As I am using tmux just for the scrollback and paste
> capabilities I am not worried with losing sessions.
>
> Maybe I'll write a suckless multiplexer for this sometime.
>
Hint: I think what you're looking for could be already o
It works! As I am using tmux just for the scrollback and paste
capabilities I am not worried with losing sessions.
Maybe I'll write a suckless multiplexer for this sometime.
On Wed, Apr 16, 2014 at 06:36:15AM +0200, Christoph Lohmann wrote:
> Greetings.
>
> On Wed, 16 Apr 2014 06:36:15 +0200 Ama
Greetings.
On Wed, 16 Apr 2014 06:36:15 +0200 Amadeus Folego
wrote:
> Hi Guys, thank you for your feedback and taking your time to
> help me!
>
> I identified the issue.
>
> It looks like I am spawning st with tmux (e.g. st -e tmux), and the issue is
> that tmux is reparenting the process id t
Yeah, I think you're right, that's why I said I'll have to find another
way to have scrolling.
But at least we should warn on the section we recommend tmux as a viable
multiplexer about this, what do you think?
On Tue, Apr 15, 2014 at 05:53:13PM -0700, Ryan O’Hara wrote:
> On Tue, Apr 15, 2014 at
On Tue, Apr 15, 2014 at 5:36 PM, Amadeus Folego wrote:
> It looks like I am spawning st with tmux (e.g. st -e tmux), and the issue is
> that tmux is reparenting the process id to tmux's daemon. Example:
>
> tmux
> |
> \_newsbeuter
> |
> \_vim st.c
>
> It is not an issue with
Hi Guys, thank you for your feedback and taking your time to
help me!
I identified the issue.
It looks like I am spawning st with tmux (e.g. st -e tmux), and the issue is
that tmux is reparenting the process id to tmux's daemon. Example:
tmux
|
\_newsbeuter
|
\_vim st.c
It
On 2014-04-15 18:44 +0200, Markus Wichmann wrote:
> st reacted to the DELETE_WINDOW message by killing the shell with
> SIGHUP. Now, your shell may ignore SIGHUP, since it is waiting for
> mutt to finish. Or it may die. If it died and sent mutt the SIGHUP,
> too, that would be great, however, some
On Thu, Apr 10, 2014 at 05:03:33PM -0300, Amadeus Folego wrote:
> I probably discovered why this happens.
>
> The WM_DELETE_WINDOW command is being received with success, I tested
> it.
>
> The issue is that the command xmonad uses to spawn st double-forks the
> process, making the SIGHUP signal
> The issue is that the command xmonad uses to spawn st double-forks the
> process, making the SIGHUP signal not being sent to the correct pid. See
> [1].
Uh. I think this is a fault of momad, but, do you know why another
terminal emulators work fine even with this double fork?
Regards,
--
I probably discovered why this happens.
The WM_DELETE_WINDOW command is being received with success, I tested
it.
The issue is that the command xmonad uses to spawn st double-forks the
process, making the SIGHUP signal not being sent to the correct pid. See
[1].
So the question remains if we sho
On Thu, Apr 10, 2014 at 08:08:51PM +0200, Roberto E. Vargas Caballero wrote:
> > 1. If you open a program like mutt, ssh, or newsbeuter and kill the
> > window with the wm (like xmonad) the process will not be killed.
>
> I think it is a bug, because in this case a SIGHUP should be sent to the
> p
> 1. If you open a program like mutt, ssh, or newsbeuter and kill the
> window with the wm (like xmonad) the process will not be killed.
I think it is a bug, because in this case a SIGHUP should be sent to the
process. How do you kill the terminal?
> 2. When installing packages with yaourt it han
Hi Guys,
I wanted some help to understand some things that happen with me using
st 0.5 that are kinda new, (coming from urxvt and other terms), these are:
1. If you open a program like mutt, ssh, or newsbeuter and kill the
window with the wm (like xmonad) the process will not be killed.
2. When
16 matches
Mail list logo
