Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #207350 > unrolled thread

Re: terminal with right-click = paste?

Back to article view | Back to linux.debian.user

Contents

  Re: terminal with right-click = paste? bw <bwtnguy@yahoo.com> - 2019-04-12 06:00 +0200
    Re: terminal with right-click = paste? Lee <ler762@gmail.com> - 2019-04-12 08:00 +0200
      Re: terminal with right-click = paste? <tomas@tuxteam.de> - 2019-04-12 10:10 +0200
        Re: terminal with right-click = paste? Lee <ler762@gmail.com> - 2019-04-12 23:10 +0200

#207350 — Re: terminal with right-click = paste?

In-Reply-To: <CAD8GWsvwWYrv jnB6DLtpWkTYR fskL8UW2UiMS3HUfBjObi2Q@mail.gmail.com>

>What I have now:
>XTerm*.Translations:

See, this is one place where I get confused, and find documentation 
lacking.  I often get different results using one of these...

xterm*whatever
xterm.whatever
xterm*VT100.whatever
xterm.vt100.whatever
*VT100.whatever

It seems there are different ways to match these resource descripters.  
The caps as well as the * and . make a difference also in how they match.

I'm not sure if it's regex, which I am real limited in, or some other 
voodoo that has some better documentation than the xterm manpage, because 
I have read the manpage and I just don't get it.

[toc] | [next] | [standalone]

#207354

On 4/11/19, bw <bwtnguy@yahoo.com> wrote:
> In-Reply-To: <CAD8GWsvwWYrv jnB6DLtpWkTYR
> fskL8UW2UiMS3HUfBjObi2Q@mail.gmail.com>
>
>>What I have now:
>>XTerm*.Translations:
>
> See, this is one place where I get confused, and find documentation
> lacking.  I often get different results using one of these...
>
> xterm*whatever
> xterm.whatever
> xterm*VT100.whatever
> xterm.vt100.whatever
> *VT100.whatever
>
> It seems there are different ways to match these resource descripters.
> The caps as well as the * and . make a difference also in how they match.
>
> I'm not sure if it's regex, which I am real limited in, or some other
> voodoo that has some better documentation than the xterm manpage, because
> I have read the manpage and I just don't get it.

I don't understand it yet either.  But it sure looks like some kind of
pattern matching, so I'm guessing that
  XTerm*.whatever
sets the property regardless of what the xterm is pretending to be vs.
  XTerm*vt100.whatever
would set the property only if the xterm is pretending to be a VT100.

It seems like I'd want my settings regardless of what the xterm is
pretending to be, so I'm going with XTERM* settings.  (altho it looks
like there's only two choices - vt100 and tek4014 & I doubt I'll ever
want to emulate a tektronics terminal)

The difference between XTerm.vt100.whatever and XTerm*vt100.whatever
is explained in the man page:

       The following resources are specified as part of the vt100
widget (class VT100).
       They are specified by patterns such as
       “XTerm.vt100.NAME”.

       If your xterm is configured to support the “toolbar”, then
those patterns need an
       extra level for the form-widget which holds the toolbar and
vt100 widget.  A
       wildcard between the top-level “XTerm” and the “vt100” widget makes the
       resource settings work for either, e.g., “XTerm*vt100.NAME”.

so apparently there's something like XTerm.toolbar.vt100.xxx resources?

As for upper/lower case - I dunno.  I copied from the example in the
man page but I just did a quick search & it has

    NOTE: some resource files use patterns such as
        *font: fixed
    which are overly broad, affecting both
        xterm.vt100.font
    and
        xterm.vt100.utf8Fonts.font
    which is probably not what you intended.

so I don't know if case is significant or no

Lee

[toc] | [prev] | [next] | [standalone]

#207357

[Multipart message — attachments visible in raw view] — view raw

On Fri, Apr 12, 2019 at 01:56:36AM -0400, Lee wrote:

[...]

> As for upper/lower case - I dunno.  I copied from the example in the
> man page but I just did a quick search & it has
> 
>     NOTE: some resource files use patterns such as
>         *font: fixed
>     which are overly broad, affecting both
>         xterm.vt100.font
>     and
>         xterm.vt100.utf8Fonts.font
>     which is probably not what you intended.
> 
> so I don't know if case is significant or no

Typically, an object (application, widget within an app, etc.) has
a lower-case name, where object classes have an upper case name.

The result is that it often doesn't matter whether you target an
object or its whole class in the resource specification.

A good primer (with links) is in the Wikipedia [1]

Cheers
[1] https://en.wikipedia.org/wiki/X_resources
-- t

[toc] | [prev] | [next] | [standalone]

#207404

On 4/12/19, tomas@tuxteam.de <tomas@tuxteam.de> wrote:
> On Fri, Apr 12, 2019 at 01:56:36AM -0400, Lee wrote:
>
>> so I don't know if case is significant or no
>
> Typically, an object (application, widget within an app, etc.) has
> a lower-case name, where object classes have an upper case name.
>
> The result is that it often doesn't matter whether you target an
> object or its whole class in the resource specification.

Thanks - that got me looking in the right place.

It turns out you need to _not_ be too general.  Originally I had
  XTerm*Translations: #override \
and got warnings every time I started an xterm.  Apparently I was also
changing the translations for menus or something..
Change it to
  XTerm*VT100.Translations: #override \
and no more error messages.

Same deal with setting XTerm*geometry and seeing only a small bit of
the popup menu.

I still haven't found a doc describing the button modifiers - eg
                 ~Meta <Btn1Down>:select-start() \n\
  !Lock Ctrl @Num_Lock <Btn1Down>:popup-menu(mainMenu) \n\

If anybody knows where the modifiers (Meta, Ctrl, Lock, etc) and
qualifiers (~!@ etc) are documented, please share.

Where I am now - a usable xterm, no error messages, left
double-clicking on a filename selects the whole filename,
right-clicking pastes the text and <ctrl>left/middle/right click&hold
brings up the appropriate menu popup

$ cat .Xresources
XTerm*faceName: DejaVu Sans Mono
XTerm*faceSize: 12

XTerm*scrollBar: true
XTerm*rightScrollBar: true

XTerm*VT100.geometry: 120x24
! NOTE: XTerm*geometry: NxN  also changes the popup menu size!

XTerm*VT100.Translations: #override \
     ~Ctrl ~Meta <Btn1Down>:  select-start() \n\
     ~Ctrl ~Meta <Btn1Motion>:select-extend() \n\
     ~Ctrl ~Meta <Btn1Up>:    select-end(PRIMARY, CUT_BUFFER0) \n\
     ~Ctrl ~Meta <Btn3Down>:  ignore() \n\
     ~Ctrl ~Meta <Btn3Up>:    insert-selection(SELECT, CUT_BUFFER0) \n
! --- maybe this is applicable?
! https://www.x.org/archive/X11R7.6/doc/man/man5/Compose.5.xhtml
!   Each modifier consists of a specified modifier and a state:
!     (! MODIFIER ) | None
!   Modifiers may be preceded by a "~" character to indicate that the
modifier must not be present.

XTerm*VT100.charClass: 45-47:48,95:48,126:48
! I like being able to double-click on a filename & having the text selected
! So add dash (45), period (46), slash (47), underscore (95) and tilde (126)
! to the aplhanumeric character class (48)
!   man xterm
!   / int charClass
! the number below the character is the character class
! notice that all the letters & digits are character class 48
!
! $ echo -n "-./_~" | od -a -td1
! 0000000    -    .    /    _    ~
!           45   46   47   95  126
! 0000005


Lee

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web