On Thu, Oct 11, 2018 at 03:27:30PM -0400, Wayne wrote:
> On Thu, Oct 11, 2018 at 03:20:49PM -0400, Wayne wrote:
> >
> > When UseThreeDMenus is defined in .ctwmrc it appears that the text of
> > menu is shifted down by some number of pixels causing the menu text
> > not to line with the menu
On Thu, Oct 11, 2018 at 03:20:49PM -0400, Wayne wrote:
>
> When UseThreeDMenus is defined in .ctwmrc it appears that the text of
> menu is shifted down by some number of pixels causing the menu text
> not to line with the menu selection and is aesthetically unpleasing.
>
> If I remove the
On Mon 08 Oct 2018 at 20:40:55 -0400, Steve Litt wrote:
> Contrastingly, ctwm keeps the windows on a given workspace in a ring
> buffer. This requires two different keystrokes: One to navigate
> clockwise, and one to navigate counterclockwise. For whatever reason,
> even after 2 months using
On Thu, Oct 11, 2018 at 07:08:07PM -0500, Matthew D. Fuller wrote:
> On Thu, Oct 11, 2018 at 03:20:49PM -0400 I heard the voice of
> Wayne, and lo! it spake thus:
> >
> > When UseThreeDMenus is defined in .ctwmrc it appears that the text
> > of menu is shifted down by some number of pixels
I typically run Vile (http://www.invisible-island.net/vile/vile.html)
in an rxvt window but occasionally I run it using it's native Xwindow
interface (xvile).
I use these settings to visually track window focus:
BorderColor "red"
BorderTileForeground "#d7d7d7"
BorderTileBackground "#d7d7d7"
On Thu, Oct 11, 2018 at 03:20:49PM -0400 I heard the voice of
Wayne, and lo! it spake thus:
>
> When UseThreeDMenus is defined in .ctwmrc it appears that the text
> of menu is shifted down by some number of pixels causing the menu
> text not to line with the menu selection and is aesthetically
> I wanted to be able to type into the partly covered window
> [...]
> It would have been intolerable to always have to bring the
> text window to the top in order to provide text input. So
> in that context, the mouse was used to interact with the
> program being tested and demonstrated and
