Am Dienstag, den 07.08.2018, 14:15 +0200 schrieb Kornel Benko:
> Works nice. The localization is super.
Thanks. I am glad to hear Qt localization works for you this time.
Jürgen
>
> Kornel
signature.asc
Description: This is a digitally signed message part
Am Dienstag, 7. August 2018 12:19:31 CEST schrieb Juergen Spitzmueller
:
> commit 7efdf98fc8f0d4d78d4c9db0e268004a95f03a40
> Author: Juergen Spitzmueller
> Date: Tue Aug 7 12:14:45 2018 +0200
>
> Further extend Info insets:
> * Add time type (time, modtime, fixtime)
On Sat, May 06, 2017 at 09:25:53AM +0200, Tommaso Cucinotta wrote:
> On 06/05/2017 02:02, Scott Kostyshak wrote:
> > Yes please revert. I remember there being some disagreement about the
> > file formats patch. I could be wrong though. Please see my questions
> > here:
>
> reverted, those 2 patche
On 06/05/2017 02:02, Scott Kostyshak wrote:
Yes please revert. I remember there being some disagreement about the
file formats patch. I could be wrong though. Please see my questions
here:
reverted, those 2 patches remain available in my
tommaso features/2.3.0alpha
branch, thanks.
On Sat, May 06, 2017 at 12:55:02AM +0200, Tommaso Cucinotta wrote:
> On 06/05/2017 00:38, Tommaso Cucinotta wrote:
> > rebased and pushed to my feature branch features/2.3.0alpha
>
> my bad,
No problem.
> in pushing the release notes for gnuplot scripts, these
> two also slipped along, I forgot
On 06/05/2017 00:38, Tommaso Cucinotta wrote:
rebased and pushed to my feature branch features/2.3.0alpha
my bad, in pushing the release notes for gnuplot scripts, these
two also slipped along, I forgot my local master was temporarily
"topped-up" ... shall we revert ?
or, would you like to pla
On 04/05/2017 17:54, Kornel Benko wrote:
2) commit cb7a69b1
Author: Tommaso Cucinotta
Date: Wed Oct 19 11:18:10 2016 +0200
Tolerate formats that are not supported by lyx2lyx.>
Yes.
rebased and pushed to my feature branch features/2.3.0alpha
3) commit bf3cda7b
Author: Tommaso Cucino
Am Donnerstag, 4. Mai 2017 um 01:06:44, schrieb Tommaso Cucinotta
> As we're on this, a few other things I had in my tommaso/master [1], out of
> which:
> I'd really love to have 3)...
> about 2) I'm stuck with recurring to Emacs-editing the first line of a .lyx
> file every time I face that is
On Thu, May 04, 2017 at 09:29:49AM +0200, Tommaso Cucinotta wrote:
> On 04/05/2017 01:45, Scott Kostyshak wrote:
> > > I'd really love to have 3)...
> >
> > Is it polished? Is there a trac ticket for this one? Or an archived
> > discussion?
>
> http://www.lyx.org/trac/ticket/5962
Thanks.
I woul
On 04/05/2017 01:45, Scott Kostyshak wrote:
I'd really love to have 3)...
Is it polished? Is there a trac ticket for this one? Or an archived
discussion?
http://www.lyx.org/trac/ticket/5962
thanks,
T.
On Thu, May 04, 2017 at 01:06:44AM +0200, Tommaso Cucinotta wrote:
> As we're on this, a few other things I had in my tommaso/master [1], out of
> which:
> I'd really love to have 3)...
Is it polished? Is there a trac ticket for this one? Or an archived
discussion?
> about 2) I'm stuck with recu
As we're on this, a few other things I had in my tommaso/master [1], out of
which:
I'd really love to have 3)...
about 2) I'm stuck with recurring to Emacs-editing the first line of a .lyx
file every time I face that issue :-)...
just pushed 1), needs to be tried by someone
guess 4) might be
On Sun, Mar 26, 2017 at 03:46:59PM +0200, Guillaume MM wrote:
> Le 21/03/2017 à 00:04, Enrico Forestieri a écrit :
> > commit 16d5c49b383841826d1bc563e2d392e12e497ed8
> > Author: Enrico Forestieri
> > Date: Mon Mar 20 23:59:16 2017 +0100
> >
> >
Le 21/03/2017 à 00:04, Enrico Forestieri a écrit :
commit 16d5c49b383841826d1bc563e2d392e12e497ed8
Author: Enrico Forestieri
Date: Mon Mar 20 23:59:16 2017 +0100
Further amendment to 72a488d7
Rephrase positively the check box for the output of en- and em-dashes
and disable it
On 18/04/13 05:35, Liviu Andronic wrote:
> Tommaso should know more about this, but this specific feature is
> already been discussed in a different thread on lyx-devel. Feel free
> to join there.
Yes, and please have a look at this
http://www.lyx.org/trac/ticket/7964
plus scan recent messages
Dear Akshay,
On Wed, Apr 17, 2013 at 9:31 AM, Akshay Nautiyal wrote:
> hello every one. i went through the project details of the task that
> requires us to make a chat /data sharing panel for lyx.I request someone to
> put me through to the mentor so that he can give insight on the way the
> pr
hello every one. i went through the project details of the task that
requires us to make a chat /data sharing panel for lyx.I request someone to
put me through to the mentor so that he can give insight on the way the
project needs to be implemented .I have a decent knowledge of qt networking
and ha
On Wed, Apr 17, 2013 at 4:56 AM, Pavel Sanda wrote:
> Liviu Andronic wrote:
>> On Thu, Apr 11, 2013 at 9:20 PM, Pavel Sanda wrote:
>> > Liviu Andronic wrote:
>> >> the question is who else is willing to volunteer for a mentorship?
>> >
>> > I'm currently looking for ledpar/ledmac project student
Hi Pavel,
I don't remember if there is a hard deadline for signing up as a mentor.
However, it looks like we definitely are going to have many student
applications, so we may get applications for all project proposals on the
LyX wiki. This means we should have all the mentors who are listed the
Liviu Andronic wrote:
> On Thu, Apr 11, 2013 at 9:20 PM, Pavel Sanda wrote:
> > Liviu Andronic wrote:
> >> the question is who else is willing to volunteer for a mentorship?
> >
> > I'm currently looking for ledpar/ledmac project student at my uni.
> >
> Excellent. Could you register on Google Mel
On Fri, Apr 12, 2013 at 10:43 AM, Tommaso Cucinotta wrote:
> I dropped a few of the proposed ideas on
>
>
> http://wiki.lyx.org/Devel/SummerOfCode2013Ideas#sDevel.SummerOfCode2013Ideas
>
> but of course I don't mean to mentor more than 1 project. Also, for the
> interactivity projects, it would b
On 11/04/13 21:04, Liviu Andronic wrote:
> Sounds great. Would you mind registering on Google Melange?
Done.
I dropped a few of the proposed ideas on
http://wiki.lyx.org/Devel/SummerOfCode2013Ideas#sDevel.SummerOfCode2013Ideas
but of course I don't mean to mentor more than 1 project. Also,
This was actually asked so many times on the list... Would you be
willing to mentor?
8) Someone goes through the whole sources and make finally some
documentation for the key structures with nice pictures for all the
metrics, cursor stuff and lfun processing structures etc similar to
http://wiki
On 11/04/13 23:34, stefano franchi wrote:
> My understanding is that the formal contract will be between
> Lyx---represented by the admins (Liviu and myself)---and the student(s).
> There is no formal contract involving the mentors.
Good, then there should be no problems for me to mentor.
> To
On Thu, Apr 11, 2013 at 12:24 PM, Tommaso Cucinotta wrote:
> 3) improve Advanced F&R, making it fast, usable, non-failing in corner
> cases, namely
>implement what is now there as a proof of concept. This can be done in
> 2 ways:
>3.a) build a find engine within various insets, able to ma
On Thu, Apr 11, 2013 at 10:04 PM, Liviu Andronic wrote:
> On Thu, Apr 11, 2013 at 9:24 PM, Tommaso Cucinotta
> wrote:
> > On 11/04/13 20:00, Liviu Andronic wrote:
> >>> This was actually asked so many times on the list... Would you be
> willing to mentor?
> >>>
> >> Those interested please let me
Le 11/04/13 21:27, Nico Williams a écrit :
Here's my (8), really my #1: 3-way diff/merge support.
Indeed. One could start by fine tuning normal diff to make it more usable.
JMarc
On Thu, Apr 11, 2013 at 9:24 PM, Tommaso Cucinotta wrote:
> On 11/04/13 20:00, Liviu Andronic wrote:
>>> This was actually asked so many times on the list... Would you be willing
>>> to mentor?
>>>
>> Those interested please let me know (in private, if you prefer). Regards,
>
> I'd be happy to me
On Thu, Apr 11, 2013 at 9:20 PM, Pavel Sanda wrote:
> Liviu Andronic wrote:
>> the question is who else is willing to volunteer for a mentorship?
>
> I'm currently looking for ledpar/ledmac project student at my uni.
>
Excellent. Could you register on Google Melange?
Thanks,
Liviu
Here's my (8), really my #1: 3-way diff/merge support.
On 11/04/13 20:00, Liviu Andronic wrote:
>> This was actually asked so many times on the list... Would you be willing to
>> mentor?
>>
> Those interested please let me know (in private, if you prefer). Regards,
I'd be happy to mentor, then, one of the ideas I dropped on the list!
However, do you
Liviu Andronic wrote:
> the question is who else is willing to volunteer for a mentorship?
I'm currently looking for ledpar/ledmac project student at my uni.
P
On Thu, Apr 11, 2013 at 8:18 PM, Pavel Sanda wrote:
> Tommaso Cucinotta wrote:
>> 6) Enhance LyX with remotely interactive writing capabilities, namely allow
>> multiple
>>users to work remotely and interactively on the same document. Solve
>> issues due to
>>conflicting editing, having
Tommaso Cucinotta wrote:
> 6) Enhance LyX with remotely interactive writing capabilities, namely allow
> multiple
>users to work remotely and interactively on the same document. Solve
> issues due to
>conflicting editing, having a way to avoid them from the ground up, or
> have a GUI
>
depending
on search options.
4) isolate part of the functionality of LyX (notably the equation editor)
within a
reusable QLyX element, that can be used for building other applications, see
5).
5) LyX enhanced CHAT client. May be built as a stand-alone application, rather
than
havi
Am Sonntag, den 17.10.2010, 18:28 +0200 schrieb Pavel Sanda:
> John McCabe-Dansted wrote:
> > > the most problematic cases of our copy&paste typically happen when
> > > middle button is used for getting, or puting stuff from/into another
> > > applications and when more lyx instances are used. dunn
> ok, thanks for the info. unless Vincent put it in, i will do before
> beta goes out.
>
I looked at the patch again and in the Qt Docs and I read:
{{{
void QClipboard::dataChanged () [signal]
This signal is emitted when the clipboard data is changed.
On Mac OS X and with Qt version 4.3 or hig
Pavel Sanda wrote:
> hi,
status update #1, the most urgent bug is gone.
> 1) short resume for things we need before releasing beta
> - Richard has some pending work on lyx2lyx which will finish some JMarc work.
> - pending patch from Gregory Jefferis for CT, Vincent might have look on it.
htt
Am 17.10.2010 21:57, schrieb Vincent van Ravesteijn:
Why would closing trunk for new features _assure_ getting a beta out ?
This prevents us from introducing new bugs and regressions. (An example of a newly introduced
regression is for example http://www.lyx.org/trac/ticket/6943)
At some po
Uwe Stöhr wrote:
> Nice! But to assure that we achieve this can you close trunk for new
> features soon? Trunk should only be open for bugfixes and documentation.
basically it is releasing beta which makes closure for new features. its not
such big deal if there are bugs in beta1, everybody will
Op 17-10-2010 20:31, Uwe Stöhr schreef:
> to sum it up, beta is doable
> at the end of October or on the very beginning of November - now for
real.
Nice! But to assure that we achieve this can you close trunk for new
features soon? Trunk should only be open for bugfixes and documentation.
> to sum it up, beta is doable
> at the end of October or on the very beginning of November - now for real.
Nice! But to assure that we achieve this can you close trunk for new features soon? Trunk should
only be open for bugfixes and documentation.
regards Uwe
Richard Heck wrote:
>> Richard, was the last movement in lyx2lyx fixing this or we wait for
>> something else?
>>
>>
> No, that was JMarc's other request. I'll have a look early next week at
> this bit.
thanks, give me hint once its finished ;)
pavel
On 10/17/2010 12:52 PM, Pavel Sanda wrote:
Pavel Sanda wrote:
Richard Heck wrote:
I've lost track, I'm afraid, of which patch set is which. Here's what I've
got.
i have flagged this message from JMarc in case it makes the things more clear:
I would like to have the ne
Uwe Stöhr wrote:
> > i tried to be transparent and listed exactly 4 bugs which are in my
> opinion
> > before-beta stuff
>
> So I missed this post from you but cannot find it in the archives. What are
> these 4 bugs?
the first point of this thread
http://www.mail-archive.com/lyx-devel@lists.lyx
> i tried to be transparent and listed exactly 4 bugs which are in my opinion
> before-beta stuff
So I missed this post from you but cannot find it in the archives. What are
these 4 bugs?
thanks and regards
Uwe
Pavel Sanda wrote:
> Richard Heck wrote:
> > I've lost track, I'm afraid, of which patch set is which. Here's what I've
> > got.
>
> i have flagged this message from JMarc in case it makes the things more clear:
>
> >I would like to have the newlineisparbreak part, which is important for
> >swea
John McCabe-Dansted wrote:
> > the most problematic cases of our copy&paste typically happen when
> > middle button is used for getting, or puting stuff from/into another
> > applications and when more lyx instances are used. dunno whether
> > the patch affects these use cases... its very fragile s
Am 14.10.2010 um 17:19 schrieb BH:
> On Wed, Oct 13, 2010 at 12:13 PM, John McCabe-Dansted
> wrote:
>> Hi, a patch for #6597 is sitting at:
>> http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
>>
>> I'd like to get this patch in. We discussed the patch and agreed it
>> lo
On Thu, Oct 14, 2010 at 11:53 PM, Pavel Sanda wrote:
>> I've tested the patch on Mac OS 10.6, current svn of LyX trunk, and
>> Qt-4.7. Cutting and pasting both from LyX to other programs and from
>> other programs to LyX works fine from what I can see.
>
> the most problematic cases of our copy&pa
BH wrote:
> > Would someone with MacOS X like to confirm that this patch doesn't
> > break pasting into LyX from other applications?
>
> I've tested the patch on Mac OS 10.6, current svn of LyX trunk, and
> Qt-4.7. Cutting and pasting both from LyX to other programs and from
> other programs to Ly
On Wed, Oct 13, 2010 at 12:13 PM, John McCabe-Dansted wrote:
> Hi, a patch for #6597 is sitting at:
> http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
>
> I'd like to get this patch in. We discussed the patch and agreed it
> looked "pretty reasonable", but there was some th
Uwe Stöhr wrote:
> > Uwe, I don't like the pressure you make.
>
> Sorry. I don't want to pressurize anybody.
no problem, asked for feedback and got it :) your impulse closed many bug
yesterday so good move anyway.
i tried to be transparent and listed exactly 4 bugs which are in my opinion
before-
Le 13 oct. 10 à 15:16, Pavel Sanda a écrit :
i see. so the question becomes how it is with funding from lyx
(JMarc?) and
I have no idea about the funding. Lars knows, or maybe José.
how many people would be interested in coming in nov/dec. (?)
some weekend is possible for me when i know it i
Am 13.10.2010 um 15:16 schrieb Pavel Sanda:
> Uwe Stöhr wrote:
>> We should and cannot rely on others. Linux distribution and all together only
>> cover less than 10% of the whole PC market.
>
> of course we are not anybody's slave. but we can do things in more or less
> clever way as far as dist
Hi, a patch for #6597 is sitting at:
http://www.lyx.org/trac/attachment/ticket/6597/GuiClipboard.cpp.2.patch
I'd like to get this patch in. We discussed the patch and agreed it
looked "pretty reasonable", but there was some theoretical discussion
as to whether the patch would break cut-and-paste
Uwe Stöhr wrote:
> We should and cannot rely on others. Linux distribution and all together only
> cover less than 10% of the whole PC market.
of course we are not anybody's slave. but we can do things in more or less
clever way as far as distros is concerned. thats why i want to have bugs solved
Uwe Stöhr wrote:
> In my opinion we need the beta and feature freeze right now because
releasing beta every 2 weeks doesn't solve anything because the main problem is
not absence of bug reports but the fact that most of us have no time for fixing
them.
freezing is good idea and i already retarget
Pavel Sanda wrote:
> i was not so much concerned about synchronous releases but with releasing
> at least one interim release before becoming more consevative...
Ah, OK. Then we are in line.
Jürgen
Richard Heck wrote:
> I've lost track, I'm afraid, of which patch set is which. Here's what I've
> got.
i have flagged this message from JMarc in case it makes the things more clear:
>I would like to have the newlineisparbreak part, which is important for
>sweave support and is a file format cha
Jürgen Spitzmüller wrote:
> Concerning the synchronouos release time: depends on what bugs show up in
> branch. If we fix some critical bug in branch, we should not wait with the
> release for the beta.
i was not so much concerned about _synchronous_ releases but with releasing
at least one inte
Richard Heck wrote:
> I also remember there was something about passthru layouts and paragraph
> breaks. I don't quite recall what that was, but it should be fairly easy,
> if someone can remind me what I was supposed to do. ;-)
the original thread is here:
http://www.mail-archive.com/lyx-devel@
On 10/12/2010 08:34 AM, Pavel Sanda wrote:
hi,
1) short resume for things we need before releasing beta
- Richard has some pending work on lyx2lyx which will finish some JMarc work.
I've lost track, I'm afraid, of which patch set is which. Here's what
I've got.
One thing I remember is a
Pavel Sanda wrote:
> 2) ideas how to deal with so many bugs we have
> i was thinking that dev meeting could have this topic - to get rid at least
> worst cases of bugs of 2.0svn. however there was no new message about the
> freiburg party - do i understand correctly this idea is dead, right?
I rea
hi,
1) short resume for things we need before releasing beta
- Richard has some pending work on lyx2lyx which will finish some JMarc work.
- pending patch from Gregory Jefferis for CT, Vincent might have look on it.
- dispatch fixes for #6417
- #6809 - converting to older LyX versions doesn't work
Dov Feldstern schreef:
Hi!
The following patches fix the remaining manifestations of bug 5061 ("Wrong
painting of cursor after newline" http://bugzilla.lyx.org/show_bug.cgi?id=5061).
All of the situations being fixed are RTL/LTR boundary cases.
I'm quite confident the first patch is correct,
Hi!
The following patches fix the remaining manifestations of bug 5061 ("Wrong
painting of cursor after newline" http://bugzilla.lyx.org/show_bug.cgi?id=5061).
All of the situations being fixed are RTL/LTR boundary cases.
I'm quite confident the first patch is correct, and will commit it if ther
Martin Vermeer <[EMAIL PROTECTED]> writes:
> I just notice that the NeedProtect parameter is poorly named. What it
> signals is this environment _has a moving argument_. It does not signal
> that this command (inset?) needs protection because _it is fragile_.
> Proper usage like illustrated below.
On Thu, Nov 01, 2007 at 09:05:37AM +0100, [EMAIL PROTECTED] wrote:
> On Thu, 1 Nov 2007, Martin Vermeer wrote:
>
>>> By the way, please use '=' instead of a copy ctor, looks cleaner:
>
>>> + FontInfo font = inherit_font;
>
> Just a C++ check, the above still use the copy constructor, right?
> (As
Martin Vermeer wrote:
On Wed, Oct 31, 2007 at 10:28:04PM +0200, Martin Vermeer wrote:
On Wed, Oct 31, 2007 at 07:53:22PM +0100, Andre Poenitz wrote:
On Wed, Oct 31, 2007 at 06:24:22PM +0200, Martin Vermeer wrote:
// Read a font definition from given file in lyx format
// Used
[EMAIL PROTECTED] wrote:
On Thu, 1 Nov 2007, Martin Vermeer wrote:
By the way, please use '=' instead of a copy ctor, looks cleaner:
+FontInfo font = inherit_font;
Just a C++ check, the above still use the copy constructor, right?
(As opposed to assignment)
Yes.
Abdel.
On Thu, 1 Nov 2007, Martin Vermeer wrote:
By the way, please use '=' instead of a copy ctor, looks cleaner:
+ FontInfo font = inherit_font;
Just a C++ check, the above still use the copy constructor, right?
(As opposed to assignment)
/Christian
--
Christian Ridderström, +46-8-768 39
On Wed, Oct 31, 2007 at 10:28:04PM +0200, Martin Vermeer wrote:
> On Wed, Oct 31, 2007 at 07:53:22PM +0100, Andre Poenitz wrote:
> > On Wed, Oct 31, 2007 at 06:24:22PM +0200, Martin Vermeer wrote:
> > > // Read a font definition from given file in lyx format
> > > // Used for layouts
> > > -FontI
On Wed, Oct 31, 2007 at 09:30:13PM +0100, Abdelrazak Younes wrote:
> Andre Poenitz wrote:
> >On Wed, Oct 31, 2007 at 06:24:22PM +0200, Martin Vermeer wrote:
> >> // Read a font definition from given file in lyx format
> >> // Used for layouts
> >>-FontInfo lyxRead(Lexer & lex)
> >>+FontInfo lyxRead
On Wed, Oct 31, 2007 at 07:53:22PM +0100, Andre Poenitz wrote:
> On Wed, Oct 31, 2007 at 06:24:22PM +0200, Martin Vermeer wrote:
> > // Read a font definition from given file in lyx format
> > // Used for layouts
> > -FontInfo lyxRead(Lexer & lex)
> > +FontInfo lyxRead(Lexer & lex, FontInfo f)
>
Andre Poenitz wrote:
On Wed, Oct 31, 2007 at 06:24:22PM +0200, Martin Vermeer wrote:
// Read a font definition from given file in lyx format
// Used for layouts
-FontInfo lyxRead(Lexer & lex)
+FontInfo lyxRead(Lexer & lex, FontInfo f)
Should be FontInfo const &.
Or even 'void lyxRead(Lexe
On Wed, Oct 31, 2007 at 06:24:22PM +0200, Martin Vermeer wrote:
> // Read a font definition from given file in lyx format
> // Used for layouts
> -FontInfo lyxRead(Lexer & lex)
> +FontInfo lyxRead(Lexer & lex, FontInfo f)
Should be FontInfo const &.
Andre'
Attached.
I had to change the font handling in TextClass.cpp again. I changed
this originally due to a bug report by Helge, but now I changed it --
not precisely back, but again to something different. This is IMHO the
way it should be: the layout defines some font attributes, which are
then fixe
José Matos wrote:
On Wednesday 22 August 2007 13:40:09 Abdelrazak Younes wrote:
Jose, do you want me to proceed?
Yes. Please coordinate with Bo since this is his code.
I've committed it.
Abdel.
Author: younes
Date: Fri Aug 24 15:53:45 2007
New Revision: 19770
URL: http://www.lyx.org/tr
Andre Poenitz wrote:
> On Thu, Aug 23, 2007 at 01:05:27PM +0200, Alfredo Braunstein wrote:
>> >>
>> >> 2) one idea would be to use a special mark inset. This would solve b)
>> >> but not a). Aditionally, this implies that we have an undesired object
>> >> that obstacles edition. We could try to t
On Thu, Aug 23, 2007 at 01:05:27PM +0200, Alfredo Braunstein wrote:
> >>
> >> 2) one idea would be to use a special mark inset. This would solve b) but
> >> not a). Aditionally, this implies that we have an undesired object that
> >> obstacles edition. We could try to track its existence with a si
Andre Poenitz wrote:
> On Wed, Aug 22, 2007 at 04:55:13PM +0200, Alfredo Braunstein wrote:
>> Abdelrazak Younes wrote:
>>
>> > Alfredo Braunstein wrote:
>> >> Abdelrazak Younes wrote:
>> >>
>> >>> Well, at runtime, in-inset bookmark sort of work now because we
>> >>> already use the paragraph id
José Matos wrote:
On Wednesday 22 August 2007 16:04:08 Abdelrazak Younes wrote:
I guess I am talking about this bug:
http://bugzilla.lyx.org/show_bug.cgi?id=3171
This bug is irrelevant now that we have one BufferView per Buffer ;-)
If that is the case then please mark the bug as fixedintrun
Bo Peng wrote:
Bo, is that OK for you?
Sorry Bo, I did not wait because my fix to bug 3427 needed this one. I
hope you don't mind, this is just cosmetics (apart for the font bug fixing).
Test 3171 and see if you need to re-open that bug.
I tested it and found no problem. But I did not expect
On Wed, Aug 22, 2007 at 07:14:37PM +0100, José Matos wrote:
> On Wednesday 22 August 2007 18:52:25 Alfredo Braunstein wrote:
> > Care to explain?
>
> Actually I don't remember much and google is not friend. :-)
>
> If every paragraph (and insets fwiw) had an universal unique ID the
> bookmar
On Wed, Aug 22, 2007 at 04:55:13PM +0200, Alfredo Braunstein wrote:
> Abdelrazak Younes wrote:
>
> > Alfredo Braunstein wrote:
> >> Abdelrazak Younes wrote:
> >>
> >>> Well, at runtime, in-inset bookmark sort of work now because we already
> >>> use the paragraph id. What is missing is the saving
José Matos wrote:
> On Wednesday 22 August 2007 18:52:25 Alfredo Braunstein wrote:
>> Care to explain?
>
> Actually I don't remember much and google is not friend. :-)
>
> If every paragraph (and insets fwiw) had an universal unique ID the
> bookmarks would be a lot more stable, no?
I don't
On Wednesday 22 August 2007 18:52:25 Alfredo Braunstein wrote:
> Care to explain?
Actually I don't remember much and google is not friend. :-)
If every paragraph (and insets fwiw) had an universal unique ID the
bookmarks would be a lot more stable, no?
> A/
--
José Abílio
José Matos wrote:
> On Wednesday 22 August 2007 15:13:27 Alfredo Braunstein wrote:
>> But Stable/DocIterators are not edit-persistent (you need some kind of
>> registering with the buffer to adjust on user edition). Do you have some
>> ideas?
>
> We have used before the idea of using libuuid (u
> Yes. Please coordinate with Bo since this is his code.
I am keeping an eye on this, while preparing embedding patch two.
Bo
On Wednesday 22 August 2007 13:40:09 Abdelrazak Younes wrote:
> Jose, do you want me to proceed?
Yes. Please coordinate with Bo since this is his code.
> Abdel.
--
José Abílio
On Wednesday 22 August 2007 15:13:27 Alfredo Braunstein wrote:
> But Stable/DocIterators are not edit-persistent (you need some kind of
> registering with the buffer to adjust on user edition). Do you have some
> ideas?
We have used before the idea of using libuuid (universally unique
identifie
On Wednesday 22 August 2007 16:04:08 Abdelrazak Younes wrote:
> > I guess I am talking about this bug:
> > http://bugzilla.lyx.org/show_bug.cgi?id=3171
>
> This bug is irrelevant now that we have one BufferView per Buffer ;-)
If that is the case then please mark the bug as fixedintrunk. :-)
> A
On Wed, 22 Aug 2007 09:46:59 -0500
Bo Peng <[EMAIL PROTECTED]> wrote:
> > There is a dirty trick used in the handling of bookmarks: bookmark id
> > needs to be converted to pit because only the latter can be saved in
> > session. Therefore, moveToPosition is called when a buffer is closed
> > and
> > Bo, is that OK for you?
>
> Sorry Bo, I did not wait because my fix to bug 3427 needed this one. I
> hope you don't mind, this is just cosmetics (apart for the font bug fixing).
Test 3171 and see if you need to re-open that bug.
Bo
Bo Peng wrote:
I am going to work a bit on the bookmark handling if you don't mind (see
patch). The goal is to extend it to support in-inset bookmarks.
Bo, is that OK for you?
If I understand your patch correctly, you move cursor inside
moveToPosition, instead of returning a new position.
No
Abdelrazak Younes wrote:
> Alfredo Braunstein wrote:
>> Abdelrazak Younes wrote:
>>
>>> Well, at runtime, in-inset bookmark sort of work now because we already
>>> use the paragraph id. What is missing is the saving/loading of in-inset
>>> bookmark when a document is opened/closed.
>>
>> I see (
> There is a dirty trick used in the handling of bookmarks: bookmark id
> needs to be converted to pit because only the latter can be saved in
> session. Therefore, moveToPosition is called when a buffer is closed
> and switched, and we DO not want to move the cursor in this cases,
> especially for
> I am going to work a bit on the bookmark handling if you don't mind (see
> patch). The goal is to extend it to support in-inset bookmarks.
>
> Bo, is that OK for you?
If I understand your patch correctly, you move cursor inside
moveToPosition, instead of returning a new position.
There is a dir
Alfredo Braunstein wrote:
Abdelrazak Younes wrote:
Well, at runtime, in-inset bookmark sort of work now because we already
use the paragraph id. What is missing is the saving/loading of in-inset
bookmark when a document is opened/closed.
I see (missed the point) :-)
Still, you are welcome t
1 - 100 of 234 matches
Mail list logo
