> i see, enumitem module is saved as cr&lf file...
> pavel
Fixed in http://www.lyx.org/trac/changeset/36435.
;).
I accidentally set the svn property "eol-style" instead of
"svn:eol-style". Being on windows, the crlf line endings got committed
which I just wanted to prevent by setting the svn:eo
Op 22-11-2010 1:44, Sebastian Guttenberg schreef:
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
read-only flag is not set correctly?
This is the same problem as reported in bug
http://www.lyx.org/trac/ticket
Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a termi
Op 19-11-2010 19:31, Jim Oldfield schreef:
In summary, there seems to confusion between boost::bind and std::tr1::bind in
MSVC2010. I managed to find this thread which is mostly on the subject:
I had no problems compiling with msvc2010 express.
I use CMake by the way.
Vincent
I can't reproduce on Windows,
Make sure the cursor is in the bottom pane, i.e., in the one that has
only one tab. Also, make sure the file
you are closing is dirty.
Yes, I understand, I've tried over and over. The TOC just gets updated
on WinXP.
but I can on Linux. (Maybe an unitialized
>>
>> I can also reproduce after I have closed the split as follows:
>> 1. Open LyX. Create a section heading (alt-P, 2), can be empty
>> 2. Open a new document (Ctrl-N)
>> 3. Enter an "x"
>> 4. Split the screen (Alt-V, E)
>> 5. Close the split-screen document (Alt-F, C, D)
>> 6. Press "x"
>>
>> I
On Thu, Nov 18, 2010 at 10:56 PM, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
>> Which other issues are there more then ?
>
> national chars and emergency issue.
What's the problem with national chars ? If the translator knows he
shouldn't use weird things, he wi
>> JMarc: "We can add a comment in the pot file to this effect."
>>
>> (http://article.gmane.org/gmane.editors.lyx.devel/122550)
>
> its not only this issue...
> pavel
>
Which other issues are there more then ?
Vincent
On Thu, Nov 18, 2010 at 10:18 PM, Pavel Sanda wrote:
> hi,
>
> i see now we introduced "newfile" to be translatable string for newfiles.
> without context most translators will just put there some translation
> eg "nový soubor" leading to "nový soubor1.lyx".
>
> last time we discussed this it ende
>
> Vincent?
>
Yes, it's on the radar.
The fix is ok, it's exactly the same as the way we fixed it for
lyxvc().file_found_hook.
Now I started wondering what we should do if we load an emergency save
and it appears that the original file is read-only. Then we don't want
to make the loaded emerge
> BTW, why is the following lfuns AtPoint? This is only useful if the cursor
> can be inside the inset (it may be that we should rename this flag if it is
> not clear)
>
> { LFUN_GRAPHICS_RELOAD, "graphics-reload", ReadOnly | AtPoint, Edit },
>
> { LFUN_LABEL_COPY_AS_REF, "copy-label-as-reference",
Since the introduction of threaded export, the autosave function
didn't work anymore.
I fixed this in r36324-r36328.
Vincent
> Actually, though the change made in r35856 caused this crash, its doing so
> revealed that the static_cast previously made there was wrong:
Thanks, I was wondering whole evening how I could have done this wrong.
Vincent
>> This will work too I guess.
>
> In the sense of "avoid the crash"...
>
> The purpose of hasDigit() is to test for occurrences of digits to avoid spell
> check of words with digits.
> A docstring may very well contain digits coded outside the range of 0x00 ..
> 0x7F (ascii 0-9).
> Unicode conta
On Sun, Nov 14, 2010 at 1:38 AM, Pavel Sanda wrote:
> hi,
>
> as we are now in beta i increased severity of bugs which are regressions
> compared to 1.6.
>
> Edwin, could you possibly look on the tabular bugs: 6908, 7021, 7007 ?
>
> JMarc, these two seems to have somthing in comon with you ;) : 6
On Tue, Nov 16, 2010 at 7:56 AM, Stephan Witt wrote:
> The attached patch for http://www.lyx.org/trac/ticket/7026 seems to be
> correct.
When I grep for "isdigit" I see the following sollution somewhere else
in the source:
diff --git a/src/support/lstrings.cpp b/src/support/lstrings.cpp
index e
> so when are at it - r35919, what was the compil error?
> or just warn of unused var?
>
Yes, unused var, but apparently one of my compilers treated that
warning as an error.
Then, there was a warning about the statement "buf;" which has no effect.
Vincent
On Fri, Nov 12, 2010 at 7:43 PM, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
>> > this is the second time you use "(void)". why?
>> >
>> > pavel
>> >
>>
>> To avoid a warning.
>
> i see.
>
>> When was the first tim
> yes it should be under preferences. personally i would like to run always
> without this feature (dont like when crash in one window kill all other
> windows).
Hmm.. you're working on multiple documents in the same time. Why do we
have the multiple window option then in LyX ? (And I thought you
On Fri, Nov 12, 2010 at 7:20 PM, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
>> Anyone against adding this error message ?
>
> ok with me.
>
>> - if (sm.allowsInteraction() && !closeAllViews())
>> - sm.cancel();
>&
Hi,
I got hit by bug http://bugs.gentoo.org/show_bug.cgi?id=212086. It
needed some time of googling to find out what the problem was, as the
error message is not very informative:
error: invalid use of undefined type 'struct QSessionManager'
/usr/include/qt4/QtGui/qapplication.h:63: error: forwar
Debian something.
Vincent
On Fri, Nov 12, 2010 at 3:13 PM, Pavel Sanda wrote:
> Jose,
>
> is "python2" executable present in present releases of python
> or its just on specific distros? can somebody on windows try
> the existence of "python2" executable?
>
> cf #7030
>
> pavel
>
The only linux pc's I have access to now h
>can somebody on windows try the existence of "python2" executable?
No trace of it in neither 2.7 or 3.1.2 (but we supply Python ourselves
in the windows installer).
Vincent
On Fri, Nov 12, 2010 at 12:55 PM, Jürgen Spitzmüller wrote:
> Vincent van Ravesteijn wrote:
>> I think the better solution would have been to disallow the use of
>> umlauts in your name.
>
> I beg your pardon?
>
> Jürgen
>
Just joking.
Vincent
On Fri, Nov 12, 2010 at 10:41 AM, wrote:
> Author: spitz
> Date: Fri Nov 12 10:41:41 2010
> New Revision: 36258
> URL: http://www.lyx.org/trac/changeset/36258
>
> Log:
> * Author.cpp:
> - to_ascii is a bad idea if your name contains two umlauts.
> (LyX asserted on my for any docu
Op 11-11-2010 20:29, Pavel Sanda schreef:
Juergen,
the fact that we use in one dialog "Indices" and in another "Indexes" is
intended?
p
I already raised this point once, and Jurgen changed all occurrences of
Indices to Indexes after consulting some native speakers.
Is the "Indices"-string a
> There's already code that checks for an existing lyxpipe. If another
> instance of lyx is connected to the other end, a message is printed
> to that effect, otherwise it is a stale pipe (maybe a left over from
> a previous crash) and is removed.
>
> So, instead of printing a message to the consol
I thought that the rule was to ask Pavel ;).
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg163211.html
>Development moved to the beta phase which basically means we will no
more include new features and focus on polishing the current ones.
"basically" leaves room for interpretati
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
We can maybe rewrite it to use pipes. Or we can rewrite the piped code
to
Op 10-11-2010 20:14, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
http://www.gitorious.com/lyx/lyx/commit/b985f653c03ad9dbf77c9e3dadf9f6d3eeaba8ae
http://www.gitorious.com/lyx/lyx/commit/8edf37e21bfbbae23e87210b959ef9dfe5e8e81c
or find
>>
>> Pavel,
>>
>> Do you think it has a chance to make it into 2.0.0 ?
>
> I think no, if we follow the rules.
>
I thought that the rule was to ask Pavel ;).
Vincent
On Tue, Nov 9, 2010 at 2:15 PM, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
>> Does anyone have an idea on how to set up the automatic testing for LyX?
>>
>> - Shall I make a directory lyx-devel/tests/ ?
>
> firstly, _what_ is going to be tested?
> we already
> These two patches implement a single instance LyX.
>
>
> Comments ?
>
Pavel,
Do you think it has a chance to make it into 2.0.0 ?
Vincent
Hi all,
These two patches implement a single instance LyX.
I can add some preference options.
- What kind of preference do we need ?
- Do we want to include the code for QtSingleApplication in our tree ?
- We then depend on QtNetwork.dll/lib and should be included in the installers.
- The actua
>
> The copied items in the CutAndPaste stack should NOT be connected for
> update.
>
Where do we break the chain then ? Only copy the Inset, not the
RenderGraphic, but then we have to add the RenderGraphic when pasting.
Anyway, my head got a bit twisted figuring this out.
But the bug is real, v
- Show quoted text -
>> sc_ = cached_item_->connect(bind(&Impl::statusChanged, this));
>>
>> Note that the copied object has now made a connection to the SAME
>> cached_item_ as the original object because cached_item_ is A SHARED
>> POINTER.
>>
>> When the cached_item_ then signals, it signals bot
I guess that as long as an InsetGraphics is not associated with a
buffer, it makes no sense to have an associated RenderGraphic at all.
Vincent
>
> I think "make test" is traditional. Similarly "make tests" or "make
> check" though those seem less used.
'make'.. what's that ;) ?
>> - Do we want to output the results as a LyX document :P ?
>
> Sounds over-engineered. :P
But it's cool, right.
> IMHO, the most important question when ru
Does anyone have an idea on how to set up the automatic testing for LyX?
- Shall I make a directory lyx-devel/tests/ ?
- Do we want to run the tests from LyX itself ?
- Do we want to run the tests as a separate application ?
- Do we want to output the results as a LyX document :P ?
Vincent
To reproduce, see bug #6814: http://www.lyx.org/trac/ticket/6814
1. Insert more than a screen full of dummy text,
2. Insert a graphics (the file doesn't need to exist),
3. Insert more than a screen full of dummy text,
4. Save file,
5. Restart LyX,
6. Open file,
7. Select all with Ctrl+A,
8. Copy,
> Would you have a link? (or at least a time window)?
http://thread.gmane.org/gmane.editors.lyx.general/55769
But parts of it seems to be missing :S..
Vincent
>> These problems need to get fixed ;).
>
> Yes. I don't know how difficult it is.
I can tell you when I know what causes it ;).
> BTW, is this a problem only on Mac OSX platform?
>
Well, I haven't seen this yet, so I guess.
Vincent
> Yes, later.
> But read Bennetts mail in this thread.
Ah yes, sorry.
> He says it works. At the cost of nasty font render problems. These were
> already
> discussed. It depends on the display font how bad the rendering is. The root
> cause
> may be that the text fragment passed to Qt string dr
>>> To be clear: the bug is in 4.6.3 present too.
>>> That's why the patch is needed...
>>>
>>> Stephan
>>>
>>
>> Which bug are we talking about here ?
>
> The bug is described in ticket #6706.
> It's not in LyX, it's in Qt - therefore the LyX ticket
> was closed. But the problem is real.
>
> Steph
Op 7-11-2010 22:19, Jean-Marc Lasgouttes schreef:
Le 7 nov. 10 à 16:31, uwesto...@lyx.org a écrit :
Log:
stdinsets.inc, InsetERT.cpp: change "ERT" to "TeX" to be consistent -
the documentation and all other menus use consequently since LyX
1.6.0 "TeX-code"
because it turned out that ERT is a m
> To be clear: the bug is in 4.6.3 present too.
> That's why the patch is needed...
>
> Stephan
>
Which bug are we talking about here ?
Vincent
> Log:
> From what I read Qt 4.2 is dead because of new threads code
===
> --- lyx-devel/trunk/INSTALL Sat Nov 6 19:42:19 2010 (r36166)
> +++ lyx-devel/trunk/INSTALL Sat Nov 6 23:53:12 2010 (r36167)
> -LyX has been tested with all
> The attached seems to work for that bug, but I haven't tested extensively as
> I don't use Bibitems myself. Still, the approach seems right, and possible,
> since the updateBuffer() call is now from one place.
>
> As I mention in the bug report, though, there are some other issues that
> remain.
Op 6-11-2010 1:48, rgh...@lyx.org schreef:
Author: rgheck
Date: Sat Nov 6 01:48:00 2010
New Revision: 36152
URL: http://www.lyx.org/trac/changeset/36152
Log:
The beginnings of a "Programming lyx2lyx" manual, probably to be
extended to prefs2prefs, once that's working.
Why not in subdir "codin
>Ow! It sounds as if the translation isn't being done back on read in that case.
Indeed.
The label of math is written as latex, but not parsed again as such.
Vincent
Op 6-11-2010 1:10, Pavel Sanda schreef:
Pavel Sanda wrote:
hi,
even trivial 1.6 files can't be opened now.
pavel
actually even 2.0 files can't be opened now.
pavel
Richard accidentally threw away my commit to lyx2lyx.
I think it is fixed now again.
Vincent
> Sorry, but this really is a bug.
>
This is bug http://www.lyx.org/trac/ticket/7019 now.
Vincent
>> Sorry if this has come up previously but I've encountered a problem with
>> lyx equation labels (lyx-1.6.7 on linux x86_64). When I use the label 'x=1'
>> for an equation, lyx changes it to 'x=3D1'. If I edit and save the lyx
>> file in emacs, then the next time lyx opens the file, the label
first step to cure the VCS load problem
>>>
Is it now completely fixed after r36145 ?
Vincent
> The startscript routine seems to put a timeout of 18 on the process. If
> that's milliseconds, then it's only about three minutes.
>
> Richard
>
I guess three minutes is not enough when MikTeX decides to update packages.
What do we do about this ?
Vincent
On Fri, Nov 5, 2010 at 9:28 PM, Pavel Sanda wrote:
> v...@lyx.org wrote:
>> Author: vfr
>> Date: Fri Nov 5 21:24:58 2010
>> New Revision: 36140
>> URL: http://www.lyx.org/trac/changeset/36140
>>
>> Log:
>> Allow for nested setBusy calls.
>
> i had the same idea, but i stopped on the question what
> Now I've finished the patch and have a fundamental problem:
> When a document contains vcs buffer-info insets like vcs-author the reload
> crashes. The culprit is the owner_->setBusy(false); in VCS::doVCCommand().
> The cursor cannot be changed when the buffer load is in progress - it seems.
> I
On Thu, Nov 4, 2010 at 4:59 PM, wrote:
> Author: rgheck
> Date: Thu Nov 4 16:59:38 2010
> New Revision: 36067
> URL: http://www.lyx.org/trac/changeset/36067
>
> Log:
> Move generally useful routines out of lyx_2_0.py and into modules. We
> keep copying these from one file to another each new rel
I would still like to move renamebuffer from guiview to buffer. Fix the vc
problems and I'll quit the refactoring for a while.
Next fun project would be to add testcode for the buffer class. This can be
done in trunk as it won't be compiled for a release.
The features I am preparing still:
- add
It gets called again in readfile, but then with the wrong name. As discussed
in another thread we can use a single call only and use d->filename.
Op 3 nov 2010 01:06 schreef "Richard Heck" :
On 11/02/2010 02:31 AM, Stephan Witt wrote:
>
>
> After my last commit in readFile() it's "only" the issu
When starts the 2.1 cycle, by the way? After 2.0 final release?
Would 2.0 be a branch then?
we should wait for for x.y.1 so people focus on bugfixing little more.
iirc this was the case for previous releases too.
pavel
I wanted to propose to start the 2.0.x branch when you enter the
feature
Sorry, Peter already did this.
Vincent
Author: rgheck
Date: Mon Nov 1 20:37:59 2010
New Revision: 35970
URL: http://www.lyx.org/trac/changeset/35970
Log:
Fix bug #7002. I think this is correct, but Peter should check.
May I, may I ?
func_ = f;
- callInGuiThread();
+ if (theApp() == 0)
The VCS load problem is (was) twofold: 1. the parser of the document needs the
VCS state so this state (checked by file_found_hook) had to be done earlier.
=> first step, move it some lines up, above the readDocument() call.
Why does the parser need to know the state ? If the state changes,
Log: first step to cure the VCS load problem
Can I please remind you and ask you to write meaningful commit-logs. Logs
explaining why the change has been made, why the new design or solution or
implementation is better, what problem it fixed, why other solutions might be
wrong although it ma
first step to cure the VCS load problem
Can I please remind you and ask you to write meaningful commit-logs. Logs
explaining why the change has been made, why the new design or solution or
implementation is better, what problem it fixed, why other solutions might be
wrong although it may see
Yes. Ive got something. Wait
Op 1 nov 2010 14:21 schreef "Pavel Sanda" :
hi,
1. Richard, whats the status of a)? i'm basically waiting only for this.
could you give it top priority on your list if its not fixed yet?
2. Vincent could you put in the pending patch for b?
3. Gregory, you didn'
Log:
first step to cure the VCS load problem
Log:
Partially fix #5108.
Log:
Fix bug #6997
Can I please remind you and ask you to write meaningful commit-logs.
Logs explaining why the change has been made, why the new design or
solution or implementation is better, what problem it fixed, wh
> After my last commit in readFile() it's "only" the issue with
file_found_hook being called with the wrong file name in case of autosave and emergency.
> I'd like to fix it before (2) or maybe Vincent does it...
> For users of VCS I'd rate it as a serious problem - but not critical.
To ill
A slightly simpler problem is to allow users to modify the generated
preamble. Sort of the same problem, but simpler and useful as well.
Op 1 nov 2010 13:39 schreef "Yann Disser" :
On 1. Nov 2010, at 13:19, Richard Heck wrote:
> On 11/01/2010 07:56 AM, Yann Disser wrote:
>>
>> ...
I wish I had
> + 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 tra
On Wed, Oct 27, 2010 at 4:37 PM, John McCabe-Dansted 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
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
> 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
It is caused by the brackets. Wasn't this the way to indicate the context of
a string? I think you now have an empty string in the context [[...]]. This
is again translated as an empty string.
Vincent
Op 31 okt 2010 08:51 schreef "Stephan Witt" :
Am 30.10.2010 um 15:59 schrieb Stephan Witt:
>
Op 29-10-2010 17:17, Richard Heck schreef:
On 10/29/2010 10:53 AM, Vincent van Ravesteijn wrote:
Op 29-10-2010 16:22, Richard Heck schreef:
On 10/29/2010 09:20 AM, Uwe Stöhr wrote:
> With classes, this happens whenever one class has a constructor
that > takes some other type
Op 29-10-2010 16:22, Richard Heck schreef:
On 10/29/2010 09:20 AM, Uwe Stöhr wrote:
> With classes, this happens whenever one class has a constructor
that > takes some other type as an argument. So, for example, suppose we
> have:
>
> class A {
>A();
>A(int);
>};
>
> So
One last question: How do I explicitly specify that the "0" in my
patch is a pointer? I mean "0" could also refer an int or double. The
compiler doesn't complain and "0" is the default return value of
innerInsetOfType but I'm wondering why this works.
There is also a small section on this in
Op 29-10-2010 3:18, uwesto...@lyx.org schreef:
Modified: lyx-devel/trunk/src/insets/InsetTabular.cpp
==
--- lyx-devel/trunk/src/insets/InsetTabular.cpp Fri Oct 29 02:46:21 2010
(r35893)
+++ lyx-devel/trunk/src/in
> Sorry, its abdel (with my gmail address) not younes.
>
> Abdel.
You're in.
Vincent
> Yes, that was the idea. However, I got a little screwed by someone
> renaming InsetNomencl.cpp to InsetNomenclature.cpp. ;)..
>
> Well, it's either me that didn't write the scripts well enough, or Git
> has a bit uncomfortabilities (?) with deleted files and/or Windows.
> That's why I was messing
> I think you should keep 'master' in line with svn/trunk and do your personal
> commit in a new 'vfr' branch.
Yes, that was the idea. However, I got a little screwed by someone
renaming InsetNomencl.cpp to InsetNomenclature.cpp. ;)..
Well, it's either me that didn't write the scripts well enough
> perhaps kill the old ascii file (or move it to attic) so there is unambiguous
> location.
Yes, I will. I wanted to wait until this new document is somewhat
decent (I'm not sure why though).
>also you nice log about casts could be saved somewhere.
It's already in there, but I hide it in the app
You know what would be cool ?
Version Control BLAME :)... that LyX shows you the whole document
colored with when the last change was, and if you hover over with your
mouse, a popup will show, who wrote it, when he wrote it, and what his
reason was to write it (read log).
Anyone ?
Vincent
> Guess what? You fix it and all InsetDialog based dialogs will be fixed :-P
>
> Abdel.
>
I guessed something different. Something like that the author of the
InsetDialog class would increment the beauty of his design to such a
level that even this little Restore button in the lower left would
beh
Ah.. and thanks for reporting and checking upon us.
Vincent
> Hi, Vincent you suggested I report recent regressions to the list, and
> this commit was from yesterday.
Yes, I did. My suggestion was even to not create a bugreport for it.
This kind of things will be fixed very quickly.
Fixed at r35863.
Vincent
> How to do so?
> Please, can you give a short example?
>
> Stephan
>
The idea is that you can make branches easily and you can commit those
branches to the git server.
So, I work on a feature called newFeature, then I make a branch for
this one, and I can push this branch to the server.
I think
Hi all,
Just to inform you. I made a git repository on gitorious.
I will update this from svn from time to time and I'm planning to put
some personal stuff of mine in there to synchronize development on
different pc's.
I'm not that experienced yet on git, but we may use it if you want to
collabo
> For some numbers a glimpse of the old battles:
>
> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg126692.html
>
> I am surprised this was only three years ago.
>
> Andre', feeling younger suddenly.
>
Ah, we didn't have those in-depth discussions for a long time.
Anyway, on a more seriou
Hi All,
I converted the two files about Rules and Recommendation into a LyX
document. You might want to have a look at it, and put your two cents
in there about coding principle, style and so forth. It is still a bit
a mess, but I hope it will get better.
Everyone is invited to edit. Please turn
>> I did something like this for Buffer::loadLyxFile(). Where would you
>> advice to put the UI then ? I can now spit out a lot of error messages
>> according to the number the functions comes up with. In Buffer ? In
>> buffer_funcs ? In GuiView ?
>
> Any direct user interaction in src/frontends/*,
> If we are going to use dynamic casting in core code I suggest that we do
> that fully and remove our own implementation of that (asInsetCommand(),
> asInsetMath(), etc)...
>
Yes, ok.
I hope you agree with my log message in http://www.lyx.org/trac/changeset/35855.
I also found some unsafe stati
Hi,
If I reconfigure and have to wait for MikTeX to download some
packages, LyX will break the Reconfigure script due to some timeout in
SystemCall.
Vincent
Sorry. If it is this obvious you can fix it. I can't do it now.
Op 26 okt 2010 19:37 schreef "Kornel Benko" :
Missing "{", "}" ?
Kornel
> no, i dont agree here. it instantly drove me crazy that lyx was not able
> the remove emergency files by itself so please let this dialog alive.
>
> pavel
>
Well this dialog is just as frustrating :(.
Vincent
> The only safe way to use them is when you control not only "sender" and
> "receiver" but also all the code paths inbetween - i.e. basically only
> within the same function or at least not from a deeply nested function.
> And in that cases using a singular return value does the trick as well.
>
>
Committed.
Vincent
> this part of code looks little bit suspicious and i would like to have a nod
> from somebody understanding the slice&boundary business before putting it into
> trunk.
>
> pavel
>
This is just code that should be "copied" from LFUN_CHAR_FORWARD and
LFUN_CHAR_BACKWARD. The patch only forgets the D
1501 - 1600 of 3126 matches
Mail list logo
