On Sat, 13 May 2023, E Frank Ball wrote:
On Sat, May 13, 2023 at 11:44:36PM +0200, Lucio Chiappetti wrote:
> In particular (independently of fvwm ?) I am used to do quick
> copy-and-paste of text selecting it with mouse button 1 (MB1) and pasting
> with mouse button 2 (MB2). Or shift-MB1 and s
On Sat, 13 May 2023, Lucio Chiappetti wrote:
In particular (independently of fvwm ?) I am used to do quick copy-and-paste
of text selecting it with mouse button 1 (MB1) and pasting with mouse button
2 (MB2). Or shift-MB1 and shift-MB2 in my favourite editor (Hessling ...
Editor), due to a pecu
On Sun, 14 May 2023 at 22:12, Lucio Chiappetti wrote:
> So the problem is an incompatibility between xterm and fvwm syntethic
> events (or a syntax problem with PointerKey ?)
>
> Is there a solution ?
No. By default generating synthetic events is considered a security
risk. which is why so many
Am Mo den 8. Mai 2023 um 19:24 schrieb Thomas Adam:
> On Sun, 7 May 2023 at 09:08, Klaus Ethgen wrote:
> > what is the best method to react to resizing displays? Be it on beamer
> > or in a virtualbox.
> >
> > Usually, fvwm does not apply to such an event and need to be restarted.
> > But this is
On Sun, May 14, 2023 at 11:48:51PM +0100, Klaus Ethgen wrote:
> Am Mo den 8. Mai 2023 um 19:24 schrieb Thomas Adam:
> > On Sun, 7 May 2023 at 09:08, Klaus Ethgen wrote:
> > > what is the best method to react to resizing displays? Be it on beamer
> > > or in a virtualbox.
> > >
> > > Usually, fvwm
