On Sat, Nov 18, 2006 at 07:30:41AM -0600, Bo Peng wrote: > >Having the minibuffer as tollbar is ugly and eats screen real estate for > >no good reason. Should be merged with the status line. > > I agree, but having a editable status line is kind of peculiar.
Any decent editor seem to have it. In fact, even Firefox puts its 'search' line edit there nowadays - which is very convenient compared to the bulky search dialogs in other applications. > >The minibuffer is not accessible by M-x when no buffer is loaded. > > I have proposed to remove this shortcut. That's a problem by itself. > >When killing LyX in the xterm using C-c, the session file is corrupted > >and further LyX starts are impossible. > > Default values should be used. There should be many try/catch in this > part of the code, but the use of exceptions was discouraged. In any case, this one is serious. No Newbie would think of deleting .lyx/session just get LyX up. I know that exceptions are hsitorically discouraged in LyX and don't know what the current state is, however, I also fail to see why killing a LyX compiled without exceptions has to result in a corrupt 'session' file. > >I still think that the session stuff is a GUI thingy and belongs to the > >frontends and can there make use of frontend specific code. > > I can think of several reasons for that: which files to load (last > opened files) belongs to the core; Calling the core from the GUI is perfectly legal. The other way round is the outruled part. > bookmarks are hard to be handled to the GUI; Why? > and implementing session in multiple frontends is tedious. A front end could use the full support of its respective library. Most notably, for the Qt4/Gui part you seem to reinvent saveState and restoreState. Andre'
