Re: Terminal window shrinks into title bar.....
On Tue, Nov 10, 2020 at 07:46:37AM -0500, Greg Wooledge wrote: > So, if you comment out the "Mouse 4" and "Mouse 5" lines there (and > restart fvwm), I bet that would disable the WindowShade binding to > the scroll wheel. You could still activate or deactivate it through > the menus, assuming you leave those in place. In case it wasn't clear, when I say "comment out", what I really mean is "copy this config file to ~/.fvwm/config if you haven't already, and then edit ~/.fvwm/config". Don't make changes to /usr/share/fvwm/*.
Re: Terminal window shrinks into title bar.....
On Tue, Nov 10, 2020 at 11:31:22PM +1100, David wrote: > I did a quick search for a fvwm manpage and found: > https://manpages.debian.org/buster/fvwm/fvwm.1.en.html > """ > WindowShade [bool] > Toggles the window shade feature for titled windows. > Windows in the shaded state only display a title-bar. > """ > so I guess you need to unbind whatever changes that > state from your mouse button and key bindings. Very interesting. A whole entire feature that I never knew about because I'm using my legacy fvwm config file (which predates this feature and doesn't make use of it), and because my mouse doesn't have a scroll wheel in the first place. Looking at what I believe to be the default Debian fvwm config file (/usr/share/fvwm/default-config/config) I find this chunk: # TitleBar: Click to Raise, Move, Double Click to Maximize # Mouse Wheel Up/Down to WindowShade On/Off # Borders: Click to raise, Move to Resize # Root Window: Left Click - Main Menu #Right Click - WindowOps Menu #Middle Click - Window List Menu # Right click TitleBar/Borders for WindowOps Menu Mouse 1 TA RaiseMoveX Move Maximize Mouse 1 FS A RaiseMove Resize Mouse 4 TA WindowShade True Mouse 5 TA WindowShade False Mouse 1 RA Menu MenuFvwmRoot Mouse 2 RA WindowList Mouse 3 RA Menu MenuWindowOpsLong Mouse 1 IA RaiseMoveX Move "Iconify off" Mouse 3 TA Menu MenuWindowOps Mouse 3 IA Menu MenuIconOps So, if you comment out the "Mouse 4" and "Mouse 5" lines there (and restart fvwm), I bet that would disable the WindowShade binding to the scroll wheel. You could still activate or deactivate it through the menus, assuming you leave those in place.
Re: Terminal window shrinks into title bar.....
On Tue, 10 Nov 2020 at 18:21, Charlie wrote: > FVWM window manager On Tue, 10 Nov 2020 at 22:55, Carl Fink wrote: > On 11/10/20 1:58 AM, Charlie wrote: > > Sometimes I press some key combination by accident and the terminal > > window shrinks back into the title bar. > > I must have the terminology wrong, because am unable to discover how to > > reverse this behaviour. no matter what wordage is used to google. > > If anyone has an idea, it would be appreciated. > It's called "roll window up" and "roll window down," by the way. I don't usually talk about things that I'm completely ignorant of (I don't use fvwm) but here we go ... I did a quick search for a fvwm manpage and found: https://manpages.debian.org/buster/fvwm/fvwm.1.en.html """ WindowShade [bool] Toggles the window shade feature for titled windows. Windows in the shaded state only display a title-bar. """ so I guess you need to unbind whatever changes that state from your mouse button and key bindings.
Re: Terminal window shrinks into title bar.....
On 11/10/20 1:58 AM, Charlie wrote: Sometimes I press some key combination by accident and the terminal window shrinks back into the title bar. I must have the terminology wrong, because am unable to discover how to reverse this behaviour. no matter what wordage is used to google. If anyone has an idea, it would be appreciated. When I annoy myself by doing that, it's by accidentally using the mouse scroll wheel over the title bar. Scroll down over the title bar to reverse. It's called "roll window up" and "roll window down," by the way. -- Carl Fink nitpick...@nitpicking.com Read my blog at blog.nitpicking.com. Reviews! Observations!
Re: Terminal window shrinks into title bar.....
On 10/11/20 5:58 pm, Charlie wrote: From my keyboard: Debian Bulleye 5.8.0-2-amd64 FVWM window manager Sometimes I press some key combination by accident and the terminal window shrinks back into the title bar. I must have the terminology wrong, because am unable to discover how to reverse this behaviour. no matter what wordage is used to google. If anyone has an idea, it would be appreciated. TIA Charlie East Gippsland Wildlife Rehabilitators Inc.. http://www.egwildlife.com.au/ Sounds like you have a keyboard shortcut set to minimise your current window. Generic answer: Search keyboard in your menu and look through the 'window' options. If you need more, perhaps search 'keyboard shortcuts FVWM' When are you opening? Looks like we may be able to visit you shortly. We're due to visit RI shortly. -- Keith Bainbridge ke1thozgro...@gmx.com
Re: terminal window returns prompt (was: dash/bash: exec behaviour change on Buster)
On 2019-07-18 10:29, John Crawley wrote:
Hi tomas and Thomas, thanks for your input.
I think I have a basic idea of what exec does.
However, try running in a terminal:
echo $$
exec
#Then, in the new terminal:
echo $$
The two PIDs are different! (or were here)
On 2019-07-17 17:37, Thomas Schmitt wrote:
John Crawley wrote:
In Buster, the launching dash shell dies *immediately* and the bash
prompt returns, even while the new window is still open.
tomas wrote:
that most probably is due to a change
in behaviour of "x-terminal-emulator".
My suspicion too. If the x-terminal-emulator puts itself into background,
then the starting terminal ends immediately.
The Debian alternative system is just a series of symlinks.
/usr/bin/x-terminal-emulator points to
/etc/alternatives/x-terminal-emulator which in turn points to (on my
system) /usr/bin/urxvt.
It's hard to imagine a stretch>buster change in behaviour, really.
What happens if you run
x-terminal-emulator
without "exec". Does the shell prompt come back immediately ?
No. Not on Stretch. x-terminal-emulator, or a specific terminal call, in
every case the prompt waits till the called window is closed.
---
But... on Buster it depends on exactly what terminal it's currently
pointing to. I've tried a few that were on my test system and:
gnome-terminal or gnome-terminal.wrapper and lxterminal both return the
prompt immediately. (*.wrapper scripts are for x-terminal-emulator
compatibility, but don't seem to affect this issue.)
urxvt, xterm, mate-terminal{,.wrapper}, xfce4-terminal{,.wrapper} and
terminator all hold the prompt till the window is closed.
---
On my test system, at the time, x-terminal-emulator pointed to
lxterminal, so it looks as if "exec" has nothing to do with this.
I'll have to do a bit of googling about why lxterminal and
gnome-terminal's behaviour has changed like this, though. Unless you
folks have any ideas?
I'd like my scripts to work the same regardless of what terminal a user
has set as x-terminal-emulator.
It seems gnome-terminal has a complicated server-client setup, but the
immediate prompt return can be avoided with 'gnome-terminal --wait':
https://bugzilla.gnome.org/show_bug.cgi?id=707899
Lxterminal (which I was more interested in) says "all instances of the
terminal are sharing a single process" which explains that, but it can
be bypassed with '--no-remote'.
So a check if x-terminal-emulator points to lxterminal and if so adding
'--no-remote' should cover my needs. Sorry for the noise.
--
John
Re: terminal window
On Wed, 9 Dec 1998, shaul wrote: >1) I never used pppconfig but I think it strange that username/password is all >it can handle. >2) Perhaps configure the chatscript by hand ? >3) xisp has the ability to open a terminal. But then again, I never needed >this terminal. > >> hello >> I need to open a terminal window for my dial-up ppp connection. I have >> to pass more than just the username/password. I used pppconfig, but it >> wasn't enough for the extras. How do I open a terminal window for >> dial-up connections? >> thanks Install and run the minicom communication program. It's easy to setup (2 minutes), and when you dial in it shows you exactly what is sent from the the remote system.
Re: terminal window
1) I never used pppconfig but I think it strange that username/password is all it can handle. 2) Perhaps configure the chatscript by hand ? 3) xisp has the ability to open a terminal. But then again, I never needed this terminal. > hello > I need to open a terminal window for my dial-up ppp connection. I have > to pass more than just the username/password. I used pppconfig, but it > wasn't enough for the extras. How do I open a terminal window for > dial-up connections? > thanks
