Re: Patch to ANNOUNCE and README (Was: 2nd try: Adding...)

On Thu, 3 May 2007, José Matos wrote: On Thursday 03 May 2007 20:31:11 [EMAIL PROTECTED] wrote: Regarding references to known issues, I've structured it as described below. Unless objections appear, I'll apply the attached patch in a day or two. Thank you Christian, your help here is particu

Re: Patch to ANNOUNCE and README (Was: 2nd try: Adding...)

On Thursday 03 May 2007 20:31:11 [EMAIL PROTECTED] wrote: > Regarding references to known issues, I've structured it as described > below. Unless objections appear, I'll apply the attached patch in a day or > two. Thank you Christian, your help here is particularly appreciated. -- José Abílio

Patch to ANNOUNCE and README (Was: 2nd try: Adding...)

Regarding references to known issues, I've structured it as described below. Unless objections appear, I'll apply the attached patch in a day or two. Regarding known issues, the file ANNOUNCE says: As usual with a major release, a lot of work that is not directly visible has ta

Re: 2nd try: Adding a reference to ANNOUNCE (Was something else

On Tue, 24 Apr 2007, Jean-Marc Lasgouttes wrote: christian> * trunk/ANNOUNCE says something like: christian> Known bugs at release time are detailed in christian> RELEASE_NOTES, and an updated list of bugs can be found in christian> the LyX wiki at http://wiki.lyx.org/LyX/RELEASE_NOTES15Beta

Re: 2nd try: Adding a reference to ANNOUNCE (Was something else

> "christian" == christian ridderstrom <[EMAIL PROTECTED]> writes: christian> * trunk/README - this is to be read first by someone using christian> the source. It should give pointers about where to go next. christian> * trunk/ANNOUNCE - the source/copy of the announcement christian> that's s

2nd try: Adding a reference to ANNOUNCE (Was something else

I'm apparently trying to understand a moving target here, so I'll give it a second shot now that 'status' has disappeared etc. In the trunk we have: * trunk/README * trunk/ANNOUNCE * trunk/NEWS * trunk/RELEASE-NOTES where * trunk/README - this is to be read first by someone using the source. I

Re: [PATCH 1.4] user interface, 2nd try

On Sun, May 22, 2005 at 06:31:41PM +0200, Michael Schmitt wrote: > Ok, another patch. This time without the controversial inset-toggle > stuff. Please apply. Applied. thanks, john

Re: [PATCH 1.4] user interface, 2nd try

John Levon wrote: The edit menu should be kept as short as possible since it's the second most commonly used after 'Insert'. In particular, the open/close insets stuff needs to go into the View menu. Hmmm... you are right. Though "Open/Close Inset" and "View DVI" do not have much in common.

Re: [PATCH 1.4] user interface, 2nd try

On Sat, May 21, 2005 at 02:47:05PM +0200, Michael Schmitt wrote: > John, speak to us - we are awaiting your approval. The edit menu should be kept as short as possible since it's the second most commonly used after 'Insert'. In particular, the open/close insets stuff needs to go into the View men

Re: [PATCH 1.4] user interface, 2nd try

Michael Schmitt wrote: > Please apply. done. Jürgen

Re: [PATCH 1.4] user interface, 2nd try

On Sat, May 21, 2005 at 02:47:05PM +0200, Michael Schmitt wrote: > John, speak to us - we are awaiting your approval. I just got off a long couple of flights from the US, I'm afraid you must wait a little longer until I can see properly :) john

Re: [PATCH 1.4] user interface, 2nd try

Jean-Marc Lasgouttes wrote: This looks good to me, but I'll let John comment too. Just one thing: inset-toggle may not exist anymore, but we have two lfuns instead ... Wouldn't it make sense to add them to the menu? Indeed. The menus should cover all LyX features. I have created a new exte

Re: [PATCH 1.4] user interface, 2nd try

> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes: Michael> Jean-Marc, this is another attempt to correct the UI files Michael> and make them consistent. This time, I used ellipses (...) Michael> according to the KDE human interface guideline. Another text change that would be great i

Re: [PATCH 1.4] user interface, 2nd try

> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes: Michael> Jean-Marc, this is another attempt to correct the UI files Michael> and make them consistent. This time, I used ellipses (...) Michael> according to the KDE human interface guideline. This looks good to me, but I'll let John

[PATCH 1.4] user interface, 2nd try

Jean-Marc, this is another attempt to correct the UI files and make them consistent. This time, I used ellipses (...) according to the KDE human interface guideline. Please check the patch and apply - or reply. Michael Index: ChangeLog

Re: [Patch] "Improved" font handling, 2nd try.

On Mon, Oct 28, 2002 at 08:16:33PM +, John Levon wrote: > On Mon, Oct 28, 2002 at 08:39:59PM +0100, Andre Poenitz wrote: > > See attached. > > This is MUCH better. Thanks a lot. Ok. > But, when I quit, it crashed : There might easily be an "off by one" somewhere. It's not exactly very robu

Re: [Patch] "Improved" font handling, 2nd try.

On Mon, Oct 28, 2002 at 08:39:59PM +0100, Andre Poenitz wrote: > See attached. This is MUCH better. Thanks a lot. But, when I quit, it crashed : #5 #6 0x083b40bc in ?? () #7 0x08149570 in __destroy_aux (__first=0x83ce9f4, __last=0x83ce9f8) at /old/gcc-3.2/include/c++/3.2/bits/stl_construct

[Patch] "Improved" font handling, 2nd try.

See attached. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson) Index: formulabase.C === RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/fo

Re: 2nd try...

Hi Roland, Roland Krause wrote: > Ok guys, > here is my 2nd try. > Sorry for the confusion. I had looked at the document a few days > ago and must have saved it somehow... > > Also to my embarassment I must confess that I am using 0.12pre5 > at home. I will update soo