Vi Mode Bar => Status-Bar
Christoph Cullmann
cullmann at absint.com
Tue Apr 2 20:45:59 UTC 2013
Hi,
IMHO that is kind of un-clever, as all applications I know of, like our ones (Kate/KWrite) and Kile
that use KatePart show a status bar with at least line/col and the viewMode string, to allow users to see
if INS/OVR/RO/...
I can revert the commits that remove the KateViModeBar, but on the other side, for all applications with a statusbar,
the vi mode bar is just a waste of one screen line and duplicated code...
Couldn't KDevelop at least show the viewMode (and update on viewModeChanged)?
Greetings
Christoph
----- Ursprüngliche Mail -----
> No, kdevelop doesn't show those status bits. We moved the line/column
> number to the top right, and the rest of the bar was rationalized
> away.
>
> 2013/4/2 Christoph Cullmann <cullmann at absint.com>:
> > Actually, the container applications should show that in the
> > viewMode.
> > Like KWrite and Kate do.
> >
> > Seems to work fine here, for the message/error I now use the
> > passive notifications.
> > Somehow KDevelop is missing any serious status bar, is that an
> > accident of my side or does it really not show any of the normal
> > status bits?
> >
> > Greetings
> > Christoph
> >
> > ----- Ursprüngliche Mail -----
> >> Hi Christoph,
> >>
> >> On Tuesday 02 Apr 2013 12:54:54 you wrote:
> >> > Hi,
> >> >
> >> > the status bar in normal kate containers should contain the
> >> > viewMode()
> >> > string (like it does in Kate and KWrite). Would you mind if I
> >> > change the vi
> >> > mode to use that string to indicate the current mode instead of
> >> > the
> >> > optional extra bar? Would save screen estate and still the
> >> > current
> >> > mode
> >> > would be very visible.
> >>
> >> Would this mean removing the bar completely? It's also used to
> >> show
> >> transient
> >> Vim messages, plus the current command being executed, etc, plus I
> >> was going
> >> to add a "macro recording" status label to it, too. Where would
> >> the
> >> current
> >> mode string appear in, say, KDevelop?
> >>
> >> Erlend is probably the best person to ask about this, really -
> >> he's
> >> the Vim
> >> mode maintainer, whereas I'm just doing a few odds and ends before
> >> moving on
> >> :)
> >>
> >> Cheers,
> >> Simon
> >>
> >> > Greetings
> >> > Christoph
> >>
> >
> > --
> > ----------------------------- Dr.-Ing. Christoph Cullmann ---------
> > AbsInt Angewandte Informatik GmbH Email: cullmann at AbsInt.com
> > Science Park 1 Tel: +49-681-38360-22
> > 66123 Saarbrücken Fax: +49-681-38360-20
> > GERMANY WWW: http://www.AbsInt.com
> > --------------------------------------------------------------------
> > Geschäftsführung: Dr.-Ing. Christian Ferdinand
> > Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB
> > 11234
> > _______________________________________________
> > KWrite-Devel mailing list
> > KWrite-Devel at kde.org
> > https://mail.kde.org/mailman/listinfo/kwrite-devel
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel
>
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: cullmann at AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
More information about the KDevelop-devel
mailing list