On Fri, 5 Aug 2022, Alexander Hall wrote:
>
>
> On August 5, 2022 8:32:25 AM GMT+02:00, Brian Durant
> <[email protected]> wrote:
> >
> >
> >On Thu, 4 Aug 2022, Alexander Hall wrote:
> >
> >>
> >>
> >> On August 4, 2022 5:42:13 PM GMT+02:00, Brian Durant
> >> <[email protected]> wrote:
> >> >
> >> >
> >> >On Thu, 4 Aug 2022, Lucas wrote:
> >> >
> >> >> Brian Durant <[email protected]> wrote:
> >> >> > I have installed OpenBSD 7.1 i386 on my Lenovo T60 and am
> >> >> > experiencing a
> >> >> > couple of issues. The first is related to the following addition that
> >> >> > I
> >> >> > made to my .Xdefaults file, which works with OpenBSD 7.1 amd64
> >> >> > installs,
> >> >> > but not with the OpenBSD 7.1 i386 install on my Lenovo T60:
> >> >> > XTerm*VT100.Translations: #override\
> >> >> > Ctrl Shift <Key> C: copy-selection(CLIPBOARD) \n\
> >> >> > Ctrl Shift <Key> V: insert-selection(CLIPBOARD)
> >> >> > Any ideas how to get copy and paste working in Xterm with an i386
> >> >> > install?
> >> >>
> >> >> I don't know if it's relevant, but my Xdefaults looks like this
> >> >>
> >> >> XTerm.VT100.translations: #override \n\
> >> >> Ctrl Alt <Key>C: copy-selection(CLIPBOARD) \n\
> >> >> Ctrl Alt <Key>V: insert-selection(CLIPBOARD) \n\
> >> >> [...other stuff...]
> >> >>
> >> >> In particular, do note the "\n" after #override, which isn't present in
> >> >> your snippet. This works fine for me.
> >> >>
> >> >> Also, vi(1) is showing \xc2\xa0 before your lines, which I don't know
> >> >> if it's product of your MUA or if it's actually part of the file (it's
> >> >> a non-breaking space, aka in XML/HTML), do double-check the
> >> >> whitespaces in there.
> >> >>
> >> >> -Lucas
> >> >
> >> >Thanks for the reply. Trying a different MUA. Not sure where the extra
> >> >characters that you mention crept in, however they weren't in the
> >> >.Xdefaults file as far as I could see. I added the extra "\n\" in the
> >> >last
> >> >line as suggested, but weirdly this had no effect. Still no copy-paste in
> >> >i386.
> >>
> >> It wasn't the last line that potentially lacked "\n\", it was the first
> >> one, "#override\n\".
> >>
> >> I suspect paste actually might already work. Did you try copying from,
> >> say, Firefox, and then paste into an xterm?
> >>
> >> I strongly believe this has nothing to do with the platform.
> >>
> >> /Alexander
> >
> >Hmm. Thanks for the inspiration, but no, paste wasn't already working. I
> >have however, now got copy to work. Unfortunately, nothing I do seems to
> >sort paste out. Currently my snippet looks like this:
> >xterm.VT100.translations: #override \
> > Ctrl Shift <Key> C: copy-selection(CLIPBOARD) \n\
> > Ctrl Shift <Key> V: insert-selection(CLIPBOARD)
> >
> >The "n\" that you have in he first line shouldn't make a difference as it
> >is a comment "#", isn't it? What causes me some concern, is the apparent
> >lack of consistent behavior between architectures on this minor, but
> >irritating issue.
>
> Every example from the xterm man page uses sth like:
>
> *VT100*translations: #override \n\
>
> , and it makes sense, as # is not a comment in the resource file itself. So
> your resource value above effectively becomes
>
> "#override Ctrl Shift <Key> C: copy-selection(CLIPBOARD)
> Ctrl Shift <Key> V: insert-selection(CLIPBOARD)"
>
> instead of
>
> "#override
> Ctrl Shift <Key> C: copy-selection(CLIPBOARD)
> Ctrl Shift <Key> V: insert-selection(CLIPBOARD)"
>
> Also, while being at the edge of my confidence level here, generally
>
> XTerm*VT100*translations:
>
> With all them asterisks, usually kicks in better. YMMV though.
>
> Also, I assume the proper xrdb commands are issued to set these resource
> values.
>
> /Alexander
OK. I tried your suggestions with the "*" and "\n\" now everything is
working fine. I corrected my .Xdefaults list on my amd64 install to match,
and that works fine as well. Many thanks.
Brian
