Re: terminal with right-click = paste?
- Date: Thu, 11 Apr 2019 09:58:24 -0500
- From: David Wright <deblis@xxxxxxxxxxxxxxxxx>
- Subject: Re: terminal with right-click = paste?
On Thu 11 Apr 2019 at 01:28:18 (-0400), Lee wrote:
> On 4/10/19, David Wright wrote:
> > On Wed 10 Apr 2019 at 17:21:06 (-0400), Lee wrote:
> >> On 4/10/19, Dan Ritter wrote:
> >> > Lee wrote:
> >> >> On 4/10/19, Dan Ritter wrote:
> >> >> > Lee wrote:
> >> >> >> I installed the xfce version of debian 9 & have a terminal icon on
> >> >> >> the
> >> >> >> menu bar that starts xfce4-terminal
> >> >> >>
> >> >> >> Is there some way to configure xfce4-terminal so that a right mouse
> >> >> >> click pastes text?
> >> >> >> What I have now is right-click brings up a menu where I have to
> >> >> >> left
> >> >> >> click on paste. ick.
> >> >> >
> >> >> > Middle button is probably set to paste right now.
> >> >>
> >> >> It is!! So how do I change that setting so that right click is set to
> >> >> paste?
> >> >
> >> > You don't! The programmers didn't include that.
> >> wow. just.. wow. I wonder if that omission has anything to do with
> >> the xterm popcon graph showing about 100K users & xfce4-terminal
> >> about 28K
> >> > You can change your button mapping for all of X with xmodmap.
> >> but then everywhere I expect a right click to pull up a menu won't -
> >> correct?
> >> Oh well... I'll give xterm a try.
> > I have a mouse with a wheel, but pressing it (as opposed to scrolling
> > it) is very unreliable. I have changed the middle-click method from
> > pressing the wheel to the old-fashioned way of dealing with 2-button
> > mice: pressing both buttons at once.
> > AFAIK this change is at the level of X and doesn't depend on the term.
> > Here are the steps I used. You might need to tweak the filename
> > ~/.xsession for a DE as I use just startx and fvwm. For setting stuff
> > automatically, you need to ascertain the name of your X startup file.
> I don't know enough to appreciate all this, much less comment on it,
> but still, it looks amazing!
> $ find / -name xinput 2>/dev/null
> so another package I need to install..
> .. which breaks the login process for me :(
> $ echo xinput > ~/.xsession
> logout, try to log in, get a blank screen for a few seconds & I'm back
> at the login screen again.
> ssh in from my windows machine, rm .xsession, and I can log in on the
> debian machine again.
> Dunno if this means anything, but the last few lines in .xsession-errors.old are
> dbus-update-activation-environment: setting PWD=/home/lee
> ⎡ Virtual core pointer id=2 [master pointer (3)]
> ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
> ⎜ ↳ ImPS/2 Generic Wheel Mouse id=9 [slave pointer (2)]
> ⎣ Virtual core keyboard id=3 [master keyboard (2)]
> ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
> ↳ Power Button id=6 [slave keyboard (3)]
> ↳ Power Button id=7 [slave keyboard (3)]
> ↳ AT Translated Set 2 keyboard id=8 [slave keyboard (3)]
> Why does putting 'xinput' in my .xsession keep me from being able to
> log in & it works just fine for you?
Because, as I wrote, I use startx to run X and fvwm as my WM, so my X
session is configured with a substantial .xsession file (and the
host-specific files it calls) that I've built up over more that two
decades. So you're best to do your investigating first with the direct
commands I gave.
You've got the output of xinput quoted above, so now try
$ xinput list-props "ImPS/2 Generic Wheel Mouse"
and see what properties are available. You're likely to see
lines similar to the ones I previously quoted (snipped from here).
So then you might be able to test the effect of a line *like*
$ xinput --set-prop "ImPS/2 Generic Wheel Mouse" "libinput Middle Emulation Enabled" 1
If you get it right, it should take immediate effect.
The last step (for you) is to divine which file to *add* this line to,
which depends on your method of starting X. It's likely .xsessionrc
according to Greg who's played with this stuff (or read around it)
more then I have. It's one of the complications that arises from
the flexibility of X: anyone can build a set of interacting
configuration files to get it started just how they want it.
Were you to use my WM (fvwm) to achieve the same ends with the mouse,
we would be having a similar conversation about where to place the
commands for much the same reason: over two decades of evolution in
> > At the end of ~/.xsession I routinely put
> > xinput
A preexisting file as you can see from the snippet below.
> > Your list would look different even with the same hardware because
> > mine shows the effect of the mouse commands I have already added
> > to ~/.xsession:
> > # Pointers tend to be too sensitive.
> > # Leave the last number as 1: the other numbers are ratio'd with it.
> > xinput --set-prop "Logitech M325" "Coordinate Transformation Matrix" .3, 0, 0, 0, .3, 0, 0, 0, 1
> > # My mouse wheel is very unreliable for button 2, so use buttons 1&3.
> > xinput --set-prop "Logitech M325" "libinput Middle Emulation Enabled" 1