On Wed, 26 Jan 2022, Bijan Soleymani wrote:
On 2022-01-26 5:55 p.m., Bijan Soleymani wrote:
Actually apparently putty does support remote resizing. It just seems that
our systems lack the right termcap entries.
I managed to resize the putty window by running the command:
resize -s height widt
On Wed, 26 Jan 2022, Bijan Soleymani wrote:
On 2022-01-26 1:45 p.m., Tim Woodall wrote:
I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.
Therefore I run screen so after reconnecting I can recover to whereever
On 2022-01-26 5:55 p.m., Bijan Soleymani wrote:
Actually apparently putty does support remote resizing. It just seems
that our systems lack the right termcap entries.
I managed to resize the putty window by running the command:
resize -s height width
so:
resize -s 24 80
Also adding this:
term
On 2022-01-26 5:42 p.m., Bijan Soleymani wrote:
As far as I know this is not a screen feature. Putty controls the window
size, it is determined by the default or whatever is saved for that
session. You can change what happens when you resize the putty window on
the machine running putty. There
On 2022-01-26 1:45 p.m., Tim Woodall wrote:
I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.
Therefore I run screen so after reconnecting I can recover to whereever
I was at.
However, the PuTTY window does no
On Mi, 26 ian 22, 18:45:41, Tim Woodall wrote:
> I have to use PuTTY to connect to a debian server. For reasons that are
> outwith my control the ssh session disconnects every 24 hrs.
>
> Therefore I run screen so after reconnecting I can recover to whereever
> I was at.
>
> However, the PuTTY wi
I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.
Therefore I run screen so after reconnecting I can recover to whereever
I was at.
However, the PuTTY window does not resize to whatever it was previously.
I can fi
Hi Thomas,
On 19/10/2021 22:31, Thomas Schmitt wrote:
Seems to be considered a firmware bug of the keyboard which might become
repairable in the future:
https://bbs.archlinux.org/viewtopic.php?id=267365
Oh, yes. Even better. Worked a treat.
Thanks again
Jeff
OpenPGP_signature
Descripti
Hi,
Jeff wrote:
> KeyPress event, [...]
> keycode 248
Seems to be considered a firmware bug of the keyboard which might become
repairable in the future:
https://bbs.archlinux.org/viewtopic.php?id=267365
> https://forums.linuxmint.com/viewtopic.php?t=105326
Such old wisdom will probably
the terminal window or in file /tmp/xev.log .
Yup:
KeyPress event, serial 68, synthetic NO, window 0x661,
root 0x238, subw 0x0, time 3095352, (168,-22), root:(1030,437),
state 0x110, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes
Hi,
due to the lack of other proposals i now come up with something ancient.
If you are still running the X Window System, then there should be a
program named xev.
Start it in a dedicated terminal window which will get its verbous
text output. Redirect a copy of that output to a file:
xev
Hallo!
I picked up a second-hand Cherry MX 3 keyboard some time ago. The feel
is very good, but when it is plugged in, I can no longer scroll the
active terminal window, and the screensaver no longer activates.
I can scroll inactive terminal windows, and everything returns to normal
if I
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
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 t
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
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
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
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
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 Schmit
On 2016-09-05 09:27:06 -0700, Charlie Kravetz wrote:
> Psychological or not, it certainly works for me. By killing the job
> number, it forces it to stop on my computer.
Yes, on *your* computer. But for the OP, it appears that the
process was not killable (yet), probably because it was in
kernel
Le decadi 20 fructidor, an CCXXIV, Dutch Ingraham a écrit :
> > SIGTERM (number 15) by default while Ctrl-C sends SIGINT (number 3) by
> > default. But both have the same default action of interrupting the process.
> The last sentence is inaccurate and imprecise. See man 7 signal, and esp.
> unde
On Mon, 5 Sep 2016 17:19:38 +0200
Nicolas George wrote:
>Le decadi 20 fructidor, an CCXXIV, Charlie Kravetz a écrit :
>> I open a second terminal, then use ps -A to find the command. I can
>> kill it with "sudo kill " which kills the job number. It is not
>> always instant, but faster than ct
On Mon, Sep 05, 2016 at 05:19:38PM +0200, Nicolas George wrote:
> Le decadi 20 fructidor, an CCXXIV, Charlie Kravetz a écrit :
> SIGTERM (number 15) by default while Ctrl-C sends SIGINT (number 3) by
> default. But both have the same default action of interrupting the process.
The last sentence is
Le decadi 20 fructidor, an CCXXIV, Charlie Kravetz a écrit :
> I open a second terminal, then use ps -A to find the command. I can
> kill it with "sudo kill " which kills the job number. It is not
> always instant, but faster than ctrl-c for some things, including rsync
> and cp .
Not true.
T
On Mon, 5 Sep 2016 09:06:27 -0500
Richard Owlett wrote:
>On 9/5/2016 8:35 AM, Jonathan Dowland wrote:
>> On Mon, Sep 05, 2016 at 08:13:03AM -0500, Richard Owlett wrote:
>>> Thank you.
>>> Sometimes harware reset is the only thing.
>>> The cp command was crudded up by human error ;/
>>
>> Your
On 9/5/2016 8:35 AM, Jonathan Dowland wrote:
On Mon, Sep 05, 2016 at 08:13:03AM -0500, Richard Owlett wrote:
Thank you.
Sometimes harware reset is the only thing.
The cp command was crudded up by human error ;/
Your ^C would eventually be honoured by cp. The result will be an incomplete
copy,
On Mon, Sep 05, 2016 at 08:13:03AM -0500, Richard Owlett wrote:
> Thank you.
> Sometimes harware reset is the only thing.
> The cp command was crudded up by human error ;/
Your ^C would eventually be honoured by cp. The result will be an incomplete
copy, but the filesystem should be in a consisten
On 9/5/2016 7:28 AM, Henrique de Moraes Holschuh wrote:
On Mon, 05 Sep 2016, Richard Owlett wrote:
I realized I had miss-specified options. As data was multiple GB and target
was a USB connected flash drive I wished an immediate termination.
Usually there is no clean way to do this, and you ha
On Mon, 05 Sep 2016, Richard Owlett wrote:
> I realized I had miss-specified options. As data was multiple GB and target
> was a USB connected flash drive I wished an immediate termination.
Usually there is no clean way to do this, and you have to wait for the
process to notice the signal, and abo
The problem occurred when using cp to copy contents of one
partition to another.
I realized I had miss-specified options. As data was multiple GB
and target was a USB connected flash drive I wished an immediate
termination.
Cntl-C had no apparent result.
Closing terminal window apparently did
Bob Proulx wrote:
> Joel Roth wrote:
> > I'm running sid with i3 as window manager.
> > With Google chrome running, every few minutes,
> > the focus jumps to chrome.
>
> Is it really chrome or really chromium?
Got it! I was inadvertently activating the Windows-key
semicolon combination which is
Joel Roth wrote:
> I'm running sid with i3 as window manager.
> With Google chrome running, every few minutes,
> the focus jumps to chrome.
Is it really chrome or really chromium?
> Too bad, as chrome has been excellent in other ways.
Are you running an extension that might be popping up a wind
Hi List,
I'm running sid with i3 as window manager.
With Google chrome running, every few minutes,
the focus jumps to chrome.
Too bad, as chrome has been excellent
in other ways.
Is that a bug or the future?
--
Joel Roth
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
w
Sridhar M.A. wrote:
On Thu, Jan 29, 2009 at 10:43:08PM -0600, Dennis Wicks wrote:
The mouse will make the window bigger, but it doesn't change the font
size!!
You could try to hold down shift and use the + and - on the numerical
keypad to change the font and windowsize.
It works for
On Sat, Jan 31, 2009 at 01:05:48AM -0600, Ron Johnson wrote:
> On 01/30/2009 11:58 PM, Daniel Burrows wrote:
>> On Fri, Jan 30, 2009 at 02:51:35PM -0600, Dennis Wicks was
>> heard to say:
>>> Thanks for the insight! I'll remember to use TERM when I have to kill
>>> so errant process. It might sa
On 01/30/2009 11:58 PM, Daniel Burrows wrote:
On Fri, Jan 30, 2009 at 02:51:35PM -0600, Dennis Wicks was
heard to say:
Thanks for the insight! I'll remember to use TERM when I have to kill so
errant process. It might save me a headache in the future!
The difference between TERM and KILL, b
On Fri, Jan 30, 2009 at 02:51:35PM -0600, Dennis Wicks was
heard to say:
> Thanks for the insight! I'll remember to use TERM when I have to kill so
> errant process. It might save me a headache in the future!
The difference between TERM and KILL, btw, is that TERM asks the
program to shut dow
On Thu, Jan 29, 2009 at 10:43:08PM -0600, Dennis Wicks wrote:
>
> The mouse will make the window bigger, but it doesn't change the font
> size!!
>
xterm has a neat feature. Ctrl-right lick of the mouse in an xterm will
pop up a menu where you can choose the font size, etc. In case you need
to make
Ken Irving wrote the following on 01/30/2009 01:30 PM:
It might be useful to compare the terminal settings in the `bad' vs `good'
cases, e.g., using stty -a > bad, etc.. You might be able to find something
to tweak to fix that particular problem.
Well behaved programs should return the termi
On Fri, Jan 30, 2009 at 10:28:03AM -0600, Dennis Wicks wrote:
> Daniel Burrows wrote the following on 01/30/2009 09:46 AM:
>> On Thu, Jan 29, 2009 at 09:21:21PM -0600, Dennis Wicks was
>> heard to say:
>>> I have just discovered that the command line in a gnome terminal
Daniel Burrows wrote the following on 01/30/2009 09:46 AM:
On Thu, Jan 29, 2009 at 09:21:21PM -0600, Dennis Wicks was
heard to say:
I have just discovered that the command line in a gnome terminal window
doesn't wrap correctly. Instead of doing a line feed and continuing on
the next li
On Thu, Jan 29, 2009 at 09:21:21PM -0600, Dennis Wicks was
heard to say:
> I have just discovered that the command line in a gnome terminal window
> doesn't wrap correctly. Instead of doing a line feed and continuing on
> the next line it just returns to the beginning of the cu
On Thu, Jan 29, 2009 at 09:21:21PM -0600, Dennis Wicks wrote:
> Greetings;
>
> I have just discovered that the command line in a gnome terminal window
> doesn't wrap correctly. Instead of doing a line feed and continuing on
> the next line it just returns to the beginning of
wrote:
Greetings;
I have just discovered that the command line in a gnome terminal
window doesn't wrap correctly. Instead of doing a line feed and
continuing on the next line it just returns to the beginning of
the current line and writes over it.
As you might suspect, this does not r
command line in a gnome terminal
window doesn't wrap correctly. Instead of doing a line feed and
continuing on the next line it just returns to the beginning of the
current line and writes over it.
As you might suspect, this does not result in a valid command line!
Anybody have any ideas??
Ron Johnson wrote the following on 01/29/2009 09:56 PM:
On 01/29/2009 09:52 PM, Dennis Wicks wrote:
Ron Johnson wrote the following on 01/29/2009 09:36 PM:
On 01/29/2009 09:21 PM, Dennis Wicks wrote:
Greetings;
I have just discovered that the command line in a gnome terminal
window doesn&#
On 01/29/2009 09:52 PM, Dennis Wicks wrote:
Ron Johnson wrote the following on 01/29/2009 09:36 PM:
On 01/29/2009 09:21 PM, Dennis Wicks wrote:
Greetings;
I have just discovered that the command line in a gnome terminal
window doesn't wrap correctly. Instead of doing a line fee
Ron Johnson wrote the following on 01/29/2009 09:36 PM:
On 01/29/2009 09:21 PM, Dennis Wicks wrote:
Greetings;
I have just discovered that the command line in a gnome terminal
window doesn't wrap correctly. Instead of doing a line feed and
continuing on the next line it just returns t
On 01/29/2009 09:21 PM, Dennis Wicks wrote:
Greetings;
I have just discovered that the command line in a gnome terminal window
doesn't wrap correctly. Instead of doing a line feed and continuing on
the next line it just returns to the beginning of the current line and
writes over it.
Greetings;
I have just discovered that the command line in a gnome
terminal window doesn't wrap correctly. Instead of doing a
line feed and continuing on the next line it just returns to
the beginning of the current line and writes over it.
As you might suspect, this does not result
I created a chroot etch with xorg, gdm and gnome as described in Debian
Reference - Debian Tips sections 8.6.35.1 through 8.6.38.4. Everything
I've tested seems to work except when I open a terminal window its dead
and the xorg.conf I use with my wacom tablet works only with the
stylus
Thank you. The "bare cd" trick was what I needed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Charles Blair <[EMAIL PROTECTED]>:
> After logging in on a gnome window, I often go to "Accessories"
> and "root terminal". I have several shell variable setting and
> some other small tasks at the beginning. When I first set the
> system up, I had a file that did these things for me. How
After logging in on a gnome window, I often go to "Accessories"
and "root terminal". I have several shell variable setting and
some other small tasks at the beginning. When I first set the
system up, I had a file that did these things for me. However,
I want to change a few things and I've fo
On Wed, Jun 09, 2004 at 08:47:38AM -0500, Barry Skidmore wrote:
> I am using WindowMaker with Debian (woody), and do not like the fact
> that the
> terminal windows are not scrollable.
>
> Could someone please recommend a terminal package that has this feature?
rxvt, wterm and xterm can do it.
Apparently, _Barry Skidmore_, on 06/09/04 09:47,typed:
I am using WindowMaker with Debian (woody), and do not like the fact that the
terminal windows are not scrollable.
Could someone please recommend a terminal package that has this feature?
Thanks,
Barry
How about a simple xterm and enabling
Thanks, I am not using kde, but installed konsole as a separate package.
Barry
On Wednesday 09 June 2004 08:55, William Ballard wrote:
> On Wed, Jun 09, 2004 at 08:47:38AM -0500, Barry Skidmore wrote:
> > I am using WindowMaker with Debian (woody), and do not like the fact that
> > the terminal w
On Wed, Jun 09, 2004 at 08:47:38AM -0500, Barry Skidmore wrote:
> I am using WindowMaker with Debian (woody), and do not like the fact that the
> terminal windows are not scrollable.
>
> Could someone please recommend a terminal package that has this feature?
Since you are using KMail, why not k
I am using WindowMaker with Debian (woody), and do not like the fact that the
terminal windows are not scrollable.
Could someone please recommend a terminal package that has this feature?
Thanks,
Barry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
On Wed, Apr 04, 2001 at 05:48:08PM -0500, Nathan E Norman wrote:
> On Wed, Apr 04, 2001 at 09:27:30PM +0100, Rory Campbell-Lange wrote:
> > I'd like to change the size of the terminal window shown on screen.
> >
> > I'm a Debian newbie. I've got Debian installe
On Wed, Apr 04, 2001 at 09:27:30PM +0100, Rory Campbell-Lange wrote:
> I'd like to change the size of the terminal window shown on screen.
>
> I'm a Debian newbie. I've got Debian installed on our rather nice new
> VALinux rackmount box and I've got it hooked up
I'd like to change the size of the terminal window shown on screen.
I'm a Debian newbie. I've got Debian installed on our rather nice new
VALinux rackmount box and I've got it hooked up to a Mitsubishi TFT
flatscreen monitor. I don't have X running, and I'm doing ev
I'd like to change the size of the terminal window shown on screen.
I'm a Debian newbie. I've got Debian installed on our rather nice new
VALinux rackmount box and I've got it hooked up to a Mitsubishi TFT
flatscreen monitor. I don't have X running, and I'm doing ev
;> 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
I
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-
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
Mark
--
"A man talking sense to himself is
66 matches
Mail list logo
