Vincent van Ravesteijn | 1 Nov 02:19 2010

Re: [patch] support for multirow vertical offset

> I'm not responsible for the new tabular Apply/OK scheme. As you say, the
> problem lies within this scheme, we need to revert this scheme not
> aprticular table feature. We have much more new table features that suffer
> from this scheme, see
> http://www.lyx.org/trac/ticket/6997
>
> I committed the multirow feature before the Apply scheme was introduced and
> are disappointed that you see me guilty that multirow doesn't work yet
> perfectly with this scheme.
>

I don't think we are talking about who is guilty and who is not
(because we know Abdel ruined it ;)).

However, you introduced a new feature, multirows, and then report bug
#6985, #6958, #6999 and then you see that you don't like the apply
scheme and you report bug #6998, #6997, #7001 and then also bug #7000
for the quite related multicolumn feature.

So, wouldn't it be logical that you first try to fix the multirow bugs
and possibly the multicolumn bugs such that they work properly, then
get the dialog to work before extending the multirow feature anymore,
and introducing more ui in the table dialog, which probably won't work
as you want.

There is plenty of time to add such a relatively small feature later.

Vincent

(Continue reading)

Uwe Stöhr | 1 Nov 03:10 2010
Picon

Re: [patch] support for multirow vertical offset

Am 01.11.2010 02:19, schrieb Vincent van Ravesteijn:

 > However, you introduced a new feature, multirows, and then report bug
 > #6985, #6958, #6999 and then you see that you don't like the apply
 > scheme and you report bug #6998, #6997, #7001 and then also bug #7000
 > for the quite related multicolumn feature.

Yes, the tabular dialog had some errors and I was responsible for some of them. With the help of 
Jürgen there is now only the multirow part of#6985 left.
#6997 is about a general issue of the apply/OK scheme that cannot be solved (or marked as invalid) 
as long as Abdel responded.

> So, wouldn't it be logical that you first try to fix the multirow bugs
> and possibly the multicolumn bugs such that they work properly, then
> get the dialog to work before extending the multirow feature anymore,
> and introducing more ui in the table dialog, which probably won't work
> as you want.
> There is plenty of time to add such a relatively small feature later.

OK, so I'll try to fix the remaining part of #6985 before. I thought you are in general against the 
patch for LyX 2.0 and I want to have it in before because of the fileformat change.

regards Uwe

Vincent van Ravesteijn | 1 Nov 03:19 2010

Crash in Alert::error

Pavel, Peter,

I created bug http://www.lyx.org/trac/ticket/7002 about the fact that
LyX crashes when it tries to show an error message that has nothing to
do with exporting in threads. Like the error you get if you didn't
supply a system dir.

Vincent

Vincent van Ravesteijn | 1 Nov 06:09 2010

Re: (r35832 by "vfr") Assert when pressing letter with Split Screen and Help->LyX Functions.

On Wed, Oct 27, 2010 at 4:37 PM, John McCabe-Dansted <gmatht <at> gmail.com> wrote:
> Hi Vincent, this appears to be another recent regression, this time
> from r35832 on Monday.

Sorry John, your system is a bit off. I can reproduce with r35831 too ;)

> I then get the Assert:

This is a serious bug and needs to fixed quickly. It would be very
helpful if you could bisect further.

P.S. you don't need the LyX Functions manual. Just a new document with
only a section header where the cursor in is located will do.

Vincent

Stephan Witt | 1 Nov 07:28 2010
Picon
Picon

Re: Unicode help

Am 01.11.2010 um 05:25 schrieb Daron Wilson:

> Hi all.
> 
> I've recently started using LyX, and I've downloaded the 2.0 alpha 6 version used with Mac OS X.  I have only
one issue so far, and that concerns the use of Unicode, in particular polytonic Greek (entered using the
Polytonic Greek keyboard layout supplied by Apple).
> 
> I'm relatively new to Unicode, so I apologize upfront if my terminology or understanding of how it works is
a little off.
> 
> Whenever I input a Greek character with any kind of combining accent, the correct combination is entered,
but LyX repeats the vowel, minus the accents.  For example, trying to input circumflex-upsilon always
results in circumflex-upsilon upsilon:
> 
> ῦ always turns into ῦυ.
> 
> The same thing happens for any letter combined with accent marks.  The problem does not happen in any of the
other document editing programs on my Mac, so I'm assuming this is something within LyX itself.

You're right. More exactly it's within a library framework the LyX package contains - the Qt library,
responsible for display I/O of LyX.
It's a known problem. You may find a discussion of that here: http://www.lyx.org/trac/ticket/6706

> I have wondered if this has something to do with some kind of automatic-replacement feature in LyX, but I
don't know enough to figure it out.
> 
> Thanks in advance for any solutions or pointers in the right direction.

The solution is to fix the problem in the Qt-libraries.
(Continue reading)

Vincent van Ravesteijn | 1 Nov 07:41 2010

Re: r35960 - lyx-devel/trunk/src/insets

> +               if (binfo.empty()) {
> +                       docstring fmt = _("%1$s unknown[[InsetNote]]");
> +                       setText(bformat(fmt, from_utf8(name_)));
> +               } else

InsetNote ?

Please remember that this should be helpful for the translators to
correctly translate the unknown part.

And I have no clue what should be unknown here :S..

Vincent

Stephan Witt | 1 Nov 08:02 2010
Picon
Picon

Re: r35960 - lyx-devel/trunk/src/insets

Am 01.11.2010 um 07:41 schrieb Vincent van Ravesteijn:

>> +               if (binfo.empty()) {
>> +                       docstring fmt = _("%1$s unknown[[InsetNote]]");
>> +                       setText(bformat(fmt, from_utf8(name_)));
>> +               } else
> 
> InsetNote ?

Sorry. Should be InsetInfo. I mixed it up while trying to fix the
latest compile problems, I'll correct that.

> 
> Please remember that this should be helpful for the translators to
> correctly translate the unknown part.
> 
> And I have no clue what should be unknown here :S..

(The value of the vcs buffer-info inset indexed by name is empty.
The replacement in this case is e. g. "vcs-author unknown".
The translator has to translate the word "unknown".)
I had to lookup your smiley in some smiley table manually ;-)

I don't know how to be more helpful to the translator.

Stephan

John McCabe-Dansted | 1 Nov 08:32 2010
Picon

Re: (r35832 by "vfr") Assert when pressing letter with Split Screen and Help->LyX Functions.

On Mon, Nov 1, 2010 at 1:09 PM, Vincent van Ravesteijn <vfr <at> lyx.org> wrote:
> On Wed, Oct 27, 2010 at 4:37 PM, John McCabe-Dansted <gmatht <at> gmail.com> wrote:
>> Hi Vincent, this appears to be another recent regression, this time
>> from r35832 on Monday.
>
> Sorry John, your system is a bit off. I can reproduce with r35831 too ;)

Incidentally, I think the regression in r35832 has to do with being
able to reproduce the bug when LFUNs.lyx is marked readonly, which in
turn is because r35832 does not set the readonly flag when opening
readonly files.

>> I then get the Assert:
>
> This is a serious bug and needs to fixed quickly. It would be very
> helpful if you could bisect further.

The actual bug itself appears to have been introduced in r34826 by "rgheck".

--

-- 
John C. McCabe-Dansted

Yann Disser | 1 Nov 10:38 2010

feature request: edit tex files

Hi everybody.

I do not know where to post a feature request, so I send it to this list -- hope that's ok.

I use LyX every day at work (doing my PhD), and I am really really happy with it!

There is one thing I am missing though, since I collaborate a lot with people that I cannot convince to use
LyX: It would be awesome, if I could edit .tex files directly with LyX, instead of going through an
import-export cycle every time. First of all, import/export changes the preamble, which might be
strange to the guy who wrote it. And second, we usually work with svn, and there is no safe way of merging the
export with other people's commit. At the moment, I  do "svn up", then I import, then I edit, then I export
somewhere else, then I copy the tex-body only and paste it to the original document, and finally I do an "svn
up/commit" to merge with other changes. To repeat this many times a day can become quite tedious...

So in short: Please add a feature to edit .tex files directly. If possible, even files that only contain a
section (without preamble whatsoever) to be included elsewhere.

Thanks a lot and keep up the good work,
Yann

PS.: If this is not the place to post feature requests, please point me to where I should have put it.
Stephan Witt | 1 Nov 10:46 2010
Picon
Picon

buffer read and vcs info inset

In the current state of buffer read the vcs info inset output is broken.
The attached patch helps. Ok to apply?

But, there is one problem left.
When reading the autosave or emergency file the "wrong" pathname is passed to lyxvc().file_found_hook().
That's why the additional calls I introduced in r35937. But it's too late for info inset when called after readFile().
The real pathname should be restored and passed in readFile(). Has someone a better proposal?

Stephan
Index: src/Buffer.cpp
===================================================================
--- src/Buffer.cpp	(Revision 35961)
+++ src/Buffer.cpp	(Arbeitskopie)
 <at>  <at>  -875,6 +875,9  <at>  <at> 
 		return readFile(tmpFile);
 	}

+	// InsetInfo needs to know if file is under VCS
+	lyxvc().file_found_hook(fn);
+
 	if (readDocument(lex)) {
 		Alert::error(_("Document format failure"),
 			bformat(_("%1$s ended unexpectedly, which means"
 <at>  <at>  -884,8 +887,6  <at>  <at> 
 	}

 	d->file_fully_loaded = true;
-	// InsetInfo needs to know if file is under VCS
(Continue reading)


Gmane