Re: Help wanted: just run gxditview on your system and click
On Thu, Jul 27, 2023 at 8:59 AM G. Branden Robinson wrote: > Just run "gxditview", left-click in the big yellow canvas area, and try > to select _any_ menu item. Hi Branden, I tried this on a Fedora f33 w/XFCE (yes, I know it's old; I'm lazy) and groff 1.22.4. I can start gxditroff with no trouble, but the menu is completely unresponsive. --dds -- Rule of Warfare #1: If Brute Force isn’t working, you aren’t using enough of it.-- Isaac Arthur, SFIA
Re: Help wanted: just run gxditview on your system and click
Hi Branden, I tried gxditview on a Linux Fedora 38 installation (out-of-the-box, groff 1.22.4), everything works as expected. Left click into canvas, menu opens, I can select items and they behave as expected. Best regards, Oliver. On 27/07/2023 17:27, G. Branden Robinson wrote: Hi folks, I could swear that at one point not too long ago, gxditview's pop-up menu still worked. But now, for me, while it pops up with a left click in the viewer/canvas area as it should, no menu item can be selected. The keyboard accelerators still work, so the only feature this actually inhibits is the printing dialog.[1] But it's still an ugly wart. Does this work for anyone else? Just run "gxditview", left-click in the big yellow canvas area, and try to select _any_ menu item. I had feared that I somehow regressed this for groff 1.23, even though I knew I hadn't touched gxditview's widget management code, but I now suspect trouble elsewhere. For me, the same failure occurs with groff 1.22.4 (Debian's version), stock 1.23.0, and Git HEAD. I compiled and installed groff 1.22.3 from source, even--same problem. Then I wanted to blame a Wayland vs. Xorg issue, mumbling something to myself about event capture, but for me, it's broken in both. I therefore think that either (a) I am incorrectly remembering that this ever worked, or (b) a recent Debian package upgrade, possibly of libxaw7, libxt6, or libx11-6, regressed this. Any ideas? Regards, Branden [1] This can be worked around by giving that dialog pop-up a keyboard accelerator, too, like capital P (lowercase p is already taken). -- Dr. Oliver Corff Wittelsbacherstr. 5A 10707 Berlin G E R M A N Y Tel.: +49-30-85727260 Mail:oliver.co...@email.de
Re: Help wanted: just run gxditview on your system and click
Hi Branden, I tried a second Fedora 38 box with vanilla installation, and that shows the problem you described. For now, I cannot say where the problems are but I ran into library problems with another application, too. Best regards, Oliver. On 27/07/2023 17:27, G. Branden Robinson wrote: Hi folks, I could swear that at one point not too long ago, gxditview's pop-up menu still worked. But now, for me, while it pops up with a left click in the viewer/canvas area as it should, no menu item can be selected. The keyboard accelerators still work, so the only feature this actually inhibits is the printing dialog.[1] But it's still an ugly wart. Does this work for anyone else? Just run "gxditview", left-click in the big yellow canvas area, and try to select _any_ menu item. I had feared that I somehow regressed this for groff 1.23, even though I knew I hadn't touched gxditview's widget management code, but I now suspect trouble elsewhere. For me, the same failure occurs with groff 1.22.4 (Debian's version), stock 1.23.0, and Git HEAD. I compiled and installed groff 1.22.3 from source, even--same problem. Then I wanted to blame a Wayland vs. Xorg issue, mumbling something to myself about event capture, but for me, it's broken in both. I therefore think that either (a) I am incorrectly remembering that this ever worked, or (b) a recent Debian package upgrade, possibly of libxaw7, libxt6, or libx11-6, regressed this. Any ideas? Regards, Branden [1] This can be worked around by giving that dialog pop-up a keyboard accelerator, too, like capital P (lowercase p is already taken). -- Dr. Oliver Corff Wittelsbacherstr. 5A 10707 Berlin GERMANY Tel.: +49-30-85727260 mailto:oliver.co...@email.de
Re: Help wanted: just run gxditview on your system and click
> gxditview from 1.22.4 freshly compiled on Opensuse 15.4 works > (all menu items). Also, this is straight X11, no Wayland involved.
Re: Help wanted: just run gxditview on your system and click
> Just run "gxditview", left-click in the big yellow canvas area, > and try to select _any_ menu item. gxditview from 1.22.4 freshly compiled on Opensuse 15.4 works (all menu items).
Re: Help wanted: just run gxditview on your system and click
At 2023-07-27T12:04:31-0500, Nate Bargmann wrote: > I can confirm the menu is not responsive on Debian Bullseye but does > work properly on Bookworm, at least I can select the Open and Quit > items and get the expected result (Groff 1.22.4 on both). > > The menu also works similarly on an up-to-date Arch Linux system > (Groff 1.23). > > All three systems are running GNOME on Wayland and I launched > gxditview from the GNOME Terminal on each. Thanks, Nate! This news is great and terrible. Great, because I'm thrilled I didn't regress groff in this respect. Terrible, because it means the problem is almost certainly in X11 libraries that haven't been actively developed for 30 years, and nearly everyone who was au fait with them has either forgotten them or is dead. Maybe I should just go straight to Alan Coopersmith... In the meantime maybe I can set up a bookworm VM. Regards, Branden signature.asc Description: PGP signature
Re: Help wanted: just run gxditview on your system and click
I can confirm the menu is not responsive on Debian Bullseye but does work properly on Bookworm, at least I can select the Open and Quit items and get the expected result (Groff 1.22.4 on both). The menu also works similarly on an up-to-date Arch Linux system (Groff 1.23). All three systems are running GNOME on Wayland and I launched gxditview from the GNOME Terminal on each. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: Help wanted: just run gxditview on your system and click
Hi Robert, At 2023-07-27T11:54:13-0400, Robert Goulding wrote: > I tried to do this, but gxditview was not on my system (Crostini on a > Chromebook = Debian 11 (bullseye). On a Debian box, make sure you have the "groff" package installed, not just "groff-base". > So I compiled again from source, making sure --with-x was added to > configure -- but although the configure output said that x libraries > were found, gxditview was not built. Not a surprise; it has dependencies that few people install anymore. > One other little glitch: the configure script said that "ln -s" does > not work, so the Makefile tried to use "ln" - which caused an error > when I tried to build. I had to manually amend the Makefile to use "ln > -s" instead. That _is_ a surprise, and it's hard for me to imagine that the relevant configure check (`AC_PROG_LN_S`)[1] would fail on _any_ Debian system. Here's the test, which I snarfed out of a config.status file on my system. It looks pretty straightfoward to me (but I've been reading Bourne scripts for many years). If you want to chase this, you might try some of these commands at your shell prompt and see what fails. rm -f conf$$ conf$$.exe conf$$.file if test -d conf$$.dir; then rm -f conf$$.dir/conf$$.file else rm -f conf$$.dir mkdir conf$$.dir 2>/dev/null fi if (echo >conf$$.file) 2>/dev/null; then if ln -s conf$$.file conf$$ 2>/dev/null; then as_ln_s='ln -s' # ... but there are two gotchas: # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. # In both cases, we have to default to `cp -pR'. ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || as_ln_s='cp -pR' elif ln conf$$.file conf$$ 2>/dev/null; then as_ln_s=ln else as_ln_s='cp -pR' fi else as_ln_s='cp -pR' fi rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file rmdir conf$$.dir 2>/dev/null Regards, Branden [1] https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Particular-Programs.html signature.asc Description: PGP signature
Re: Help wanted: just run gxditview on your system and click
OK, I managed to compile gxditview. Left-clicking brings up the menu; none of the items are selectable. And I figured out the "ln -s" problem. I downloaded the tarball into my Downloads folder, which is a mounted filesystem from the point of view of the Linux container. And "ln -s" always fails in mounted filesystems. Once I built it in my home directory, there was no longer an error. On Thu, Jul 27, 2023 at 12:11 PM G. Branden Robinson < g.branden.robin...@gmail.com> wrote: > Hi Robert, > > At 2023-07-27T11:54:13-0400, Robert Goulding wrote: > > I tried to do this, but gxditview was not on my system (Crostini on a > > Chromebook = Debian 11 (bullseye). > > On a Debian box, make sure you have the "groff" package installed, not > just "groff-base". > > > So I compiled again from source, making sure --with-x was added to > > configure -- but although the configure output said that x libraries > > were found, gxditview was not built. > > Not a surprise; it has dependencies that few people install anymore. > > > One other little glitch: the configure script said that "ln -s" does > > not work, so the Makefile tried to use "ln" - which caused an error > > when I tried to build. I had to manually amend the Makefile to use "ln > > -s" instead. > > That _is_ a surprise, and it's hard for me to imagine that the relevant > configure check (`AC_PROG_LN_S`)[1] would fail on _any_ Debian system. > > Here's the test, which I snarfed out of a config.status file on my > system. It looks pretty straightfoward to me (but I've been reading > Bourne scripts for many years). > > If you want to chase this, you might try some of these commands at your > shell prompt and see what fails. > > rm -f conf$$ conf$$.exe conf$$.file > if test -d conf$$.dir; then > rm -f conf$$.dir/conf$$.file > else > rm -f conf$$.dir > mkdir conf$$.dir 2>/dev/null > fi > if (echo >conf$$.file) 2>/dev/null; then > if ln -s conf$$.file conf$$ 2>/dev/null; then > as_ln_s='ln -s' > # ... but there are two gotchas: > # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. > # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper > executable. > # In both cases, we have to default to `cp -pR'. > ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || > as_ln_s='cp -pR' > elif ln conf$$.file conf$$ 2>/dev/null; then > as_ln_s=ln > else > as_ln_s='cp -pR' > fi > else > as_ln_s='cp -pR' > fi > rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file > rmdir conf$$.dir 2>/dev/null > > Regards, > Branden > > [1] > https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Particular-Programs.html > -- Robert Goulding Director, John J. Reilly Center for Science, Technology, and Values; Assoc. Professor, Program of Liberal Studies, Fellow, Medieval Institute, University of Notre Dame.
Re: Help wanted: just run gxditview on your system and click
I tried to do this, but gxditview was not on my system (Crostini on a Chromebook = Debian 11 (bullseye). So I compiled again from source, making sure --with-x was added to configure -- but although the configure output said that x libraries were found, gxditview was not built. One other little glitch: the configure script said that "ln -s" does not work, so the Makefile tried to use "ln" - which caused an error when I tried to build. I had to manually amend the Makefile to use "ln -s" instead. On Thu, Jul 27, 2023 at 11:30 AM G. Branden Robinson < g.branden.robin...@gmail.com> wrote: > Hi folks, > > I could swear that at one point not too long ago, gxditview's pop-up > menu still worked. But now, for me, while it pops up with a left click > in the viewer/canvas area as it should, no menu item can be selected. > The keyboard accelerators still work, so the only feature this actually > inhibits is the printing dialog.[1] But it's still an ugly wart. > > Does this work for anyone else? > > Just run "gxditview", left-click in the big yellow canvas area, and try > to select _any_ menu item. > > I had feared that I somehow regressed this for groff 1.23, even though I > knew I hadn't touched gxditview's widget management code, but I now > suspect trouble elsewhere. For me, the same failure occurs with groff > 1.22.4 (Debian's version), stock 1.23.0, and Git HEAD. > > I compiled and installed groff 1.22.3 from source, even--same problem. > > Then I wanted to blame a Wayland vs. Xorg issue, mumbling something > to myself about event capture, but for me, it's broken in both. > > I therefore think that either (a) I am incorrectly remembering that this > ever worked, or (b) a recent Debian package upgrade, possibly of > libxaw7, libxt6, or libx11-6, regressed this. > > Any ideas? > > Regards, > Branden > > [1] This can be worked around by giving that dialog pop-up a keyboard > accelerator, too, like capital P (lowercase p is already taken). > -- Robert Goulding Director, John J. Reilly Center for Science, Technology, and Values; Assoc. Professor, Program of Liberal Studies, Fellow, Medieval Institute, University of Notre Dame.
