> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Tue, Oct 30, 2001 at 03:44:00PM +0100, Jean-Marc Lasgouttes
John> wrote:
>> Could you have a look to reword that too?
John> that was sloppy of me sorry !
John> Hopefully this is the last of them, please apply
It seems there were m
29 16:00:27 1.120
+++ lib/ChangeLog 2001/10/30 16:16:08
@@ -1,3 +1,7 @@
+2001-10-30 John Levon <[EMAIL PROTECTED]>
+
+ * Makefile.am: remove BUGS.lyx mention
+
2001-10-29 John Levon <[EMAIL PROTECTED]>
* ui/default.ui: remove Known Bugs entry
Index: lib/Ma
this removes the menu entry
please apply
thanks
john
--
"If the software that a company produces isn't reliable, adding a bunch of
'Mother, may I' rules to the language and the code won't fix it."
- Pete Becker
Index: lib/ChangeLog
On Wed, Jul 25, 2001 at 05:21:18AM +0100, John Levon wrote:
>
> I'm trying to basically fold the relevant parts into the bug tracker. Can people
> hint on which are these are still true ?
>
> btw, why do we not allow X pastes from us when we've not done Edit->Copy ? Aslo
> why does there seem to
On Fri, Jul 27, 2001 at 03:04:04PM +0200, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> Nothing. As I said, this problem doesn't exist in align, and
> Dekel> align is the preferred way for multi-line equations.
>
> The problem exists in most of
On Fri, Jul 27, 2001 at 03:10:24PM +0200, Jean-Marc Lasgouttes wrote:
> > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
> Andre> If aligned is indeed prefered we could as well required ams by
> Andre> default and I do not have to check everything individually. But
> Andre> I am not sure
> Nothing. As I said, this problem doesn't exist in align, and align is the
> preferred way for multi-line equations.
Jean-Marc seems to think otherwise and personally I am clueless.
If aligned is indeed prefered we could as well required ams by default and
I do not have to check everything indi
On Fri, Jul 27, 2001 at 02:37:30PM +0200, Andre Poenitz wrote:
> > > >> 21. When entering a multi-line equation, and the beginning of the
> > > >> second (or following) line begins with a "[" character, LaTeX
> > > >> sometimes gets confused. To avoid problems, it is necessary to add
> > > >> {} i
> > >> 21. When entering a multi-line equation, and the beginning of the
> > >> second (or following) line begins with a "[" character, LaTeX
> > >> sometimes gets confused. To avoid problems, it is necessary to add
> > >> {} in TeX mode just before the bracket, as in the following
> > >> example:
On Wed, Jul 25, 2001 at 10:39:33AM +0200, Jean-Marc Lasgouttes wrote:
> >> 8. When several insets are placed consecutively (this can happen
> >> with error insets), clicking on an inset can result in opening the
> >> wrong one. A workaround is to use C-o, with the cursor placed just
> >> before th
On Wed, Jul 25, 2001 at 10:39:33AM +0200, Jean-Marc Lasgouttes wrote:
Thanks JMarc !
> >> 6. The vertical scroll bar of the preamble window is broken. If you
> >> resize the window, strange things can happen, including a fatal
> >> crash! This is a bug in XForms. [Note from Jean-Marc: things are
> > 29. The pop-up browsers in the Preferences and Document Layout dialogs
> > (Edit->Preferences->Usage->Language->Default language and
> > Layout->Document->Document->Class respectively) will pop up in the wrong
> > position on the display if the dialog is moved and the browser's tab
folder is
I'm trying to basically fold the relevant parts into the bug tracker. Can people
hint on which are these are still true ?
btw, why do we not allow X pastes from us when we've not done Edit->Copy ? Aslo
why does there seem to be a limit on how much is copied ?
thanks
john
> 1. The LyX keyboard
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I'm imagining a "Framed text inset" that can wrap like a text
Angus> inset does but which is drawn with a bevelled edge (and so is
Angus> visually a button). Actually, I'm imagining a pair of these,
Angus> one non-editable that dis
On Tue, 17 Oct 2000, Juergen Vigna wrote:
> On 17-Oct-2000 Angus Leeming wrote:
> > Chewing this one to death...
> >
> > I'm picturing a grey button with a white text inset embedded in it.
> > Clicking on the grey part will launch the citation dialog. Clicking in
> > the text inset will allow the
On 17-Oct-2000 Angus Leeming wrote:
>
> Chewing this one to death...
>
> I'm picturing a grey button with a white text inset embedded in it. Clicking
> on the grey part will launch the citation dialog. Clicking in the text inset
> will allow the user to edit the comment.
>
> Will this lead
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Chewing this one to death...
The problem is that it will be a lot of work to get it to work, and
that we will only know after that whether it was a good idea :)
Angus> I'm picturing a grey button with a white text inset embedded
On Tue, 17 Oct 2000, Jean-Marc Lasgouttes wrote:
> >> Currently the remark is a plain string, so that no quoting of the
> >> latex contents is done.
> Angus> Ok, understood. So the IDEAL solution would be to have a text
> Angus> inset in the popup dialog?
> Maybe, although I like the idea of a c
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>> Currently the remark is a plain string, so that no quoting of the
>> latex contents is done.
Angus> Ok, understood. So the IDEAL solution would be to have a text
Angus> inset in the popup dialog?
Maybe, although I like the idea of a
>>>>> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
>> I think that Baruch is looking at the lib/doc/BUGS.lyx file from
>> lyx-devel, while you look at BUGS.lyx from lyx-doc, and these files
>> are not the same. We should keep this file only in
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
>> BTW, the Customization.lyx file in lyx-doc was saved using the 2.17
>> format (with a tabular inset), so you shouldn't use it for
>> 1.1.5fix2.
Allan> Bad move. All lyx-docs should be editted by the current fix
Allan> release or at least
It
> > had something to do with bad repainting of a partly obscured window, I
> > think.
>
> I think that Baruch is looking at the lib/doc/BUGS.lyx file from lyx-devel,
> while you look at BUGS.lyx from lyx-doc, and these files are not the same.
> We should keep this file on
> No, the problem is with the remarks inside [] in \cite. It should be
> possible to enter general text here with a text inset. However, I am
> not sure it is really doable. Maybe a checkbox 'add remark' in the
> popup, and then the text inset would appear inside the boxed citation
> inset (is tha
cured window, I
> think.
I think that Baruch is looking at the lib/doc/BUGS.lyx file from lyx-devel,
while you look at BUGS.lyx from lyx-doc, and these files are not the same.
We should keep this file only in one place.
BTW, the Customization.lyx file in lyx-doc was saved using the 2.17 format
> "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
Baruch> Yes. This is much better.
OK, I'll check that in.
Baruch> I understand it now. If you meant that you updated the file in
Baruch> cvs I'll update soon and check.
No, I did not. But feel free to propose an alternate wording.
JMar
On 16 Oct 2000, Jean-Marc Lasgouttes wrote:
> > "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
>
> Baruch> Copy&Paste is working, if style is not preserved its another
> Baruch> bug, but basic copy and paste is working. The wording should
> Baruch> be changed to reflect the actual bug.
> "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
Baruch> Copy&Paste is working, if style is not preserved its another
Baruch> bug, but basic copy and paste is working. The wording should
Baruch> be changed to reflect the actual bug.
Would the following be better?
12. When copying from
On 16 Oct 2000, Jean-Marc Lasgouttes wrote:
> > "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
>
> Baruch> It seems like Point 9 is till true (It is about citation inset
> Baruch> not escaping special characters on LaTeX output), this
> Baruch> shouldn't be too hard to fix though, a sim
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc, once 1.1.6 is released, I plan to go back and sort
Angus> out the citation stuff properly. Natbib etc.
Great.
Angus> Can you explain yourself a little further, therefore. Do you
Angus> mean using a text inset to store
On 16 Oct 2000, Jean-Marc Lasgouttes wrote:
> > "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
>
> Baruch> Isn't point 13 already taken care of in one of the last fix
> Baruch> rounds, it is a problem of being unable to copy&paste from lyx
> Baruch> to other X11 apps.
>
> No, being una
> The right thing would be to attach a text inset to the citation
> reference, but I do not know how easy/convenient it would be.
> Basically, the code to escape characters is already here in lyxformat
> reading/writing.
Jean-Marc, once 1.1.6 is released, I plan to go back and sort out the
citat
> "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
Baruch> Point number 4 is
Baruch> irrelevant, there is no Options->Keyboard popup anymore.
It is still here in 1.1.5fix, but I agree we can remove it right now.
Baruch> A "feature" of LyX is that when you switch a document it does
Baruch
> "R" == R Lahaye <[EMAIL PROTECTED]> writes:
R> I'll suggest to throw this into the Know Bugs documentation for the
R> time being.
Thanks. I just did it.
JMarc
I'll suggest to throw this into the Know Bugs documentation
for the time being.
I've attached a patch to the lyxdoc/BUGS.lyx document
(it only adds a summarized version of Lgb's email to the
bugs list).
If that's the place where it may go, can somebody of
the documentation
I'll suggest to throw this into the Know Bugs documentation
for the time being.
I've attached a patch to the lyxdoc/BUGS.lyx document
(it only adds a summarized version of Lgb's email to the
bugs list).
If that's the place where it may go, can somebody of
the documentation
> >> > On Wed, Oct 13, 1999 at 10:54:15PM +0200, Lars Gullik Bjønnes
> >> wrote: > > > > What BUGS.lyx should we keep? The one in
> >> lyx-devel/lib/doc/BUGS.lyx or > > lyxdoc/BUGS.lyx ? > > The one in
> >> lyxdoc makes more sense, I
>>>>> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
Kayvan> On Thu, Oct 14, 1999 at 12:59:32PM +1000, Allan Rae wrote:
>> On Wed, 13 Oct 1999, Kayvan A. Sylvan wrote:
>>
>> > On Wed, Oct 13, 1999 at 10:54:15PM +0200, Lars Gullik
On Thu, Oct 14, 1999 at 12:59:32PM +1000, Allan Rae wrote:
> On Wed, 13 Oct 1999, Kayvan A. Sylvan wrote:
>
> > On Wed, Oct 13, 1999 at 10:54:15PM +0200, Lars Gullik Bjønnes wrote:
> > >
> > > What BUGS.lyx should we keep? The one in lyx-devel/lib/doc/BUG
On Wed, 13 Oct 1999, Kayvan A. Sylvan wrote:
> On Wed, Oct 13, 1999 at 10:54:15PM +0200, Lars Gullik Bjønnes wrote:
> >
> > What BUGS.lyx should we keep? The one in lyx-devel/lib/doc/BUGS.lyx or
> > lyxdoc/BUGS.lyx ?
>
> The one in lyxdoc makes more sense, IMO.
Why
On Wed, Oct 13, 1999 at 10:54:15PM +0200, Lars Gullik Bjønnes wrote:
>
> What BUGS.lyx should we keep? The one in lyx-devel/lib/doc/BUGS.lyx or
> lyxdoc/BUGS.lyx ?
The one in lyxdoc makes more sense, IMO.
--
Kayvan Aghaiepour Sylvan | Proud husband of | Father to my kid
What BUGS.lyx should we keep? The one in lyx-devel/lib/doc/BUGS.lyx or
lyxdoc/BUGS.lyx ?
Lgb
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> When we save a file, the autosave file (bak) should be deleted
Lars> if it exists. A new autosave file should only be created if
Lars> lyx_clean is false.
Lars> So the value of bak_clean should not matter in that case.
If you
*Jean-Marc Lasgouttes writes:
| 1/ make markLyXClean() set bak_clean to true (if the .lyx file is
| clean, we don't need a backup, after all)
|
| 2/ Call markBakClean() in bufferlist::write().
|
| I think the first solution is the right one.
I am not sure how the code goes...but
When we
*Asger K Alstrup Nielsen writes:
| Argh, when you think a bit about it, you'll reach this conclusion:
|
| After we have auto-saved, the LyX clean flag should not be set to
| true. Thus, we will keep auto-saving.
|
| We need a special auto-save-clean flag. This flag should be set
| after
*Amir Karger writes:
| recreating the web site. (Although, as a rough draft for this
| particular page, you could always just use the raw text of
| LyX3-Tasks.)
That is exactly what I did in the first place.
Lgb
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> Argh, when you think a bit about it, you'll reach this
Asger> conclusion:
Asger> After we have auto-saved, the LyX clean flag should not be set
Asger> to true. Thus, we will keep auto-saving.
Right, of course.
Asger>
> Well, it seems that BakClean() is only set/tested individually in this
> autosave thing. Otherwise, the Buffer::bak_clean boolean is only
> set/reset together with lyx_clean. So I think that I will
>
> 1/ Use isLyXClean in autosave now.
>
> 2/ Later (after 1.0.0 or even in 1.1) get rid of this
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> IMO, we should use "isLyxClean()", and "isReadonly()" (it's
Asger> possible to change the status of a changed document to make it
Asger> read-only, but then I don't think we should autosave it...)
Asger> I don't know wha
> In lyx_cb.C, AutoSave() has the following code,
>
> if (current_view->currentBuffer()->isBakClean()
> || current_view->currentBuffer()->isReadonly())
> return;
> while in BufferList::QwriteAll(), we have a test like:
>
> if (!b->isLyxCl
I am not able to reproduce this, and it seems to work
Lars> correctly.
The same happened to me, but I added it to the file anyway because I don't
know much about rcs. So I guess I can remove this one.
I also notied that I was a bit supid to swithc Intro.lyx and BUGS.lyx
to book class. It som
I was looking at bug 23, which is subfigures. I actually was trying to use
subfigures yesterday, except with tables, and it failed completely.
The basic issue is that subfigures shouldn't be in the figure popup.
Subfigures are really sub*floats*, because you're allowed to have subfigures
and subt
Bug 7: I fixed this some time ago, can people check that it works,
please?
Bug 24: I am not able to reproduce this, and it seems to work
correctly.
Lgb
52 matches
Mail list logo
