Re: FVWM: acroread9 -- Where's the minimize button?
On Fri, Oct 28, 2011 at 02:12:09PM -0700, Ronald F. Guilmette wrote:
>
> Is it just me,
I would think so, since acroread is hopefully never used to view PDFs
anymore by anyone.
> containing acroread, unlike all other applications windows, fails to have
> a standard sort of minimization button in the upper right hand corner of the
> window frame?
>
> Is this is a known problem?
>
> Is there a workaround?
I know nothing about acroread, and am refusing to install it, but the only
thing I can suggest is looking in to:
MwmDecor
MwmFunctions
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
FVWM: acroread9 -- Where's the minimize button?
[ On Friday, October 28, 2011 at 14:12:09 (-0700), Ronald F. Guilmette wrote: ] > Subject: FVWM: acroread9 -- Where's the minimize button? > > > Is it just me, or has anyone else experienced an oddity where the window > containing acroread, unlike all other applications windows, fails to have > a standard sort of minimization button in the upper right hand corner of the > window frame? > > Is this is a known problem? > > Is there a workaround? buttons are working for me on a acroread window (fvwm2.5.26) You want to set Style * MWMFunctions, MWMDecor, HintOverride greets, ingo
Re: FVWM: (Icon)TitleFormat doesnt quite work like IndexedWindowName for one window
hullo, On 19 October 2011 18:51, elliot s wrote: > Version 2.6.3: > Previous versions only added the "(%t)" when there was a repeated name. > The new code always adds it. > I worked around the %t in add_window.c by checking if count was > non-zero, tho that wouldnt kill the parens, which i changed to a space > in my fvwmrc. the patch with this email i have written stops the number of window if it is 1 - but what must i do to delete the brackets? i do not like the new titleformat command because this is now very hard to do Harry patch Description: Binary data
Re: FVWM: (Icon)TitleFormat doesnt quite work like IndexedWindowName for one window
On Sat, Oct 29, 2011 at 12:37:04PM +0100, Harry portobello wrote:
> hullo,
>
> On 19 October 2011 18:51, elliot s wrote:
> > Version 2.6.3:
> > Previous versions only added the "(%t)" when there was a repeated name.
> > The new code always adds it.
> > I worked around the %t in add_window.c by checking if count was
> > non-zero, tho that wouldnt kill the parens, which i changed to a space
> > in my fvwmrc.
>
> the patch with this email i have written stops the number of window if
> it is 1 - but what must i do to delete the brackets?
The parenthesis are only by default if you explicitly use IndexedWindowName.
If you use TitleFormat directly, you're free to add whatever you want around
%t.
I'm still not going to fix this; there is nothing broken.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
Re: FVWM: acroread9 -- Where's the minimize button?
On Sat, Oct 29, 2011 at 12:27:37PM +0200, Ingo Wardinski wrote: > [ On Friday, October 28, 2011 at 14:12:09 (-0700), Ronald F. Guilmette > wrote: ] > > Subject: FVWM: acroread9 -- Where's the minimize button? > > > > > > Is it just me, or has anyone else experienced an oddity where the window > > containing acroread, unlike all other applications windows, fails to have > > a standard sort of minimization button in the upper right hand corner of > > the > > window frame? > > > > Is this is a known problem? > > > > Is there a workaround? > > buttons are working for me on a acroread window (fvwm2.5.26) > You want to set > Style * MWMFunctions, MWMDecor, HintOverride Acroread works fine for me too, I use the same Style as above and have fvwm 2.5.30 -- Frank Ball fra...@frankb.us
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Thomas Adam wrote: > So put your config somewhere with it still exhibiting the problem for you, > and I'll take a look. Hi! I will do this within the next days. I will need a little bit of time to make two easily compareable configs. I also will use this opportunity to point out another bug (FVWM does not update the window title when the new window title contains a unicode character, which always happens when I use bugzilla). Just wait until I'm back... Michael
Re: FVWM: (Icon)TitleFormat doesnt quite work like IndexedWindowName for one window
Thomas Adam wrote: > On Sat, Oct 29, 2011 at 12:37:04PM +0100, Harry portobello wrote: >> hullo, >> >> On 19 October 2011 18:51, elliot s wrote: >> > Version 2.6.3: >> > Previous versions only added the "(%t)" when there was a repeated name. >> > The new code always adds it. >> > I worked around the %t in add_window.c by checking if count was >> > non-zero, tho that wouldnt kill the parens, which i changed to a space >> > in my fvwmrc. >> >> the patch with this email i have written stops the number of window if >> it is 1 - but what must i do to delete the brackets? > [...] > > I'm still not going to fix this; there is nothing broken. Maybe, Harry should politely ask for a new feature? If there are people who need such kind of behaviour, then the specification could be extended with a new option, maybe a switch?
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Sat, Oct 29, 2011 at 10:31:52PM +0200, Michael Großer wrote:
> Thomas Adam wrote:
> > So put your config somewhere with it still exhibiting the problem for you,
> > and I'll take a look.
>
> Hi! I will do this within the next days. I will need a little bit of
> time to make two easily compareable configs. I also will use this
> opportunity to point out another bug (FVWM does not update the window
> title when the new window title contains a unicode character, which
> always happens when I use bugzilla).
You do not need to point this out, it's been a known bug for a while.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
Re: FVWM: (Icon)TitleFormat doesnt quite work like IndexedWindowName for one window
On Sat, Oct 29, 2011 at 10:38:36PM +0200, Michael Großer wrote:
> Thomas Adam wrote:
> > On Sat, Oct 29, 2011 at 12:37:04PM +0100, Harry portobello wrote:
> >> hullo,
> >>
> >> On 19 October 2011 18:51, elliot s wrote:
> >> > Version 2.6.3:
> >> > Previous versions only added the "(%t)" when there was a repeated name.
> >> > The new code always adds it.
> >> > I worked around the %t in add_window.c by checking if count was
> >> > non-zero, tho that wouldnt kill the parens, which i changed to a space
> >> > in my fvwmrc.
> >>
> >> the patch with this email i have written stops the number of window if
> >> it is 1 - but what must i do to delete the brackets?
> >
>
> [...]
>
> >
> > I'm still not going to fix this; there is nothing broken.
>
>
> Maybe, Harry should politely ask for a new feature?
> If there are people who need such kind of behaviour, then
> the specification could be extended with a new option, maybe
> a switch?
It's a count -- the number of windows matching a condition. It was a bug in
the original that it never put the number 1 there for a single instance.
Adding in a flag is confusing and rather amusing to document why. If you
*really* can't live without this, script it with FvwmEvent.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Thomas Adam wrote: > On Sat, Oct 29, 2011 at 10:31:52PM +0200, Michael Großer wrote: >> [...] I also will use this >> opportunity to point out another bug (FVWM does not update the window >> title when the new window title contains a unicode character, which >> always happens when I use bugzilla). > > You do not need to point this out, it's been a known bug for a while. Oh! When will it be fixed then? I'm confronted with this bug up to hundred times every day, because I always have to use my mouse wheel to scroll to the top of bugzilla pages just because the window title doesn't show me the description of the bug that I'm reading or editing. In my first FVWM days, I loaded an additional KDE3 session into an xnest window, but this contraption is not very stable, and I'm not able to use copy and paste between the inside and the outside of xnest, and KDE3 is dead anyway since from Debian Squeeze on a very horrible and totally unacceptable KDE4 is shipped...
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Sat, Oct 29, 2011 at 11:29:42PM +0200, Michael Großer wrote:
> Thomas Adam wrote:
> > On Sat, Oct 29, 2011 at 10:31:52PM +0200, Michael Großer wrote:
> >> [...] I also will use this
> >> opportunity to point out another bug (FVWM does not update the window
> >> title when the new window title contains a unicode character, which
> >> always happens when I use bugzilla).
> >
> > You do not need to point this out, it's been a known bug for a while.
>
> Oh! When will it be fixed then? I'm confronted with this bug up to hundred
When I get round to it.
Can you also look in to "BugOpts TransliterateUtf8"? I've had success in
the past setting that. But the fix is altogether more complex. I've a
working branch on my github FVWM repository which holds prototype fixes,
ISTR. It's probably out of date though.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Thomas Adam wrote: > On Sat, Oct 29, 2011 at 11:29:42PM +0200, Michael Großer wrote: >> Thomas Adam wrote: >> > On Sat, Oct 29, 2011 at 10:31:52PM +0200, Michael Großer wrote: >> >> [...] I also will use this >> >> opportunity to point out another bug (FVWM does not update the window >> >> title when the new window title contains a unicode character, which >> >> always happens when I use bugzilla). >> > >> > You do not need to point this out, it's been a known bug for a while. >> >> Oh! When will it be fixed then? I'm confronted with this bug up to hundred > > When I get round to it. > > Can you also look in to "BugOpts TransliterateUtf8"? I've had success in OK. One more item on my mental to-do list. But this is one I will be reminded of every day when I use bugzilla...
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Saturday, 29 October 2011 at 23:29, Michael Großer wrote: > Oh! When will it be fixed then? I'm confronted with this bug up to hundred > times every day, because I always have to use my mouse wheel to scroll > to the top of bugzilla pages just because the window title doesn't > show me the description of the bug that I'm reading or editing. If you're using Firefox, there's an addon to show the page title in the status bar.
