Re: Lyx trunk crashes on scrolling with continuous spelling on

Stefano Franchi wrote: > Thanks, John. Here is a backtrace: are you sure you have debugging symbols enabled when you did ./configure? i would expect line numbers to appear in the listing. pavel

Re: #6558: Edit->Language lacks keyboard shortcuts.

On Thu, Feb 25, 2010 at 6:07 AM, Jürgen Spitzmüller wrote: >> OK, but adding a couple of lines of code makes this much nicer for >> English users. > > But we do not only have English users. Right, but English is the language I can test with confidence. > I'm not even sure my current approach > i

Re: Lyx trunk crashes on scrolling with continuous spelling on

On 02/24/10, "John McCabe-Dansted" wrote: >On Thu, Feb 25, 2010 at 4:51 AM, Stefano Franchi > > wrote: >> backtrace if someone is willing to teach me how to convince gdb to start >> lyx with -sysdir and -userdir parameters. > > gdb lyx > run -sysdir my_sys_dir -userdir my_user_dir > >Should do

Re: Lyx trunk crashes on scrolling with continuous spelling on

Stefano Franchi wrote: > Following the recent exchanges on the lyx-user list, I gave the most recent > version of the SVN code a try (revision 33559) . Unsuccessfully, it turns > out. > Lyx crashes while scrolling a very simple document, with the following output > to console: Stefano, are you

Re: Feature proposal: inline bibtex formatted refs

On 02/24/2010 09:49 PM, Manoj Rajagopalan wrote: On Wednesday 24 February 2010 04:43:23 pm Vincent van Ravesteijn wrote: Manoj Rajagopalan schreef: 1. Is this change acceptable? I think so. 2. This feature requires the IncludeBib.py script submitted by another user/

Re: Feature proposal: inline bibtex formatted refs

On Wednesday 24 February 2010 04:43:23 pm Vincent van Ravesteijn wrote: > Manoj Rajagopalan schreef: > > 1. Is this change acceptable? > > I think so. > > > 2. This feature requires the IncludeBib.py script submitted by another > > user/developer in the issue-log on trac: > > http://www.lyx.org

Re: #6558: Edit->Language lacks keyboard shortcuts.

John McCabe-Dansted wrote: > OK, but adding a couple of lines of code makes this much nicer for > English users. But we do not only have English users. I'm not even sure my current approach is suitable for all localizations. I think Japanese uses roman accelerators, but the strings are non-rom

Re: Feature proposal: inline bibtex formatted refs

Manoj Rajagopalan schreef: 1. Is this change acceptable? I think so. 2. This feature requires the IncludeBib.py script submitted by another user/developer in the issue-log on trac: http://www.lyx.org/trac/ticket/4624 Can the IncludeBib.py script be bundled with the lyx distribution now? I

Lyx trunk crashes on scrolling with continuous spelling on

Following the recent exchanges on the lyx-user list, I gave the most recent version of the SVN code a try (revision 33559) . Unsuccessfully, it turns out. Lyx crashes while scrolling a very simple document, with the following output to console: QPainter::setFont: Painter not active QPainter::f

Feature proposal: inline bibtex formatted refs

Hi developers, I have worked out a way to get references inlined into exported .tex documents, based on suggestions from Richard Heck. It would be nice to build this feature into LyX and I am interested in contributing this change. Please help me with a few questions: 1. Is this change acce

Re: Reporting bugs on the devel-list.

John McCabe-Dansted schreef: On Thu, Feb 25, 2010 at 12:24 AM, LyX Ticket Tracker wrote: #6553: Assert on Opening the Edit menu to the left of a Math Inset PS. Why don't you report this on the devel-list. Especially if it concerns on-going business. The literal answer to

Re: Yet more static analysis: Use Coverity?

John McCabe-Dansted schreef: I found the errors reported by cppcheck much easier to fix than bug reports (e.g. generated by my keytest). For example: [./development/lyxserver/server_monitor.c:173]: (error) Memory leak: pipename This had the obvious solution of adding free(pipename) to line 17

Inset modification and dirty buffer

When modifying an inset in a document doesn't toggle the buffer dirty anymore. Vincent

Yet more static analysis: Use Coverity?

I found the errors reported by cppcheck much easier to fix than bug reports (e.g. generated by my keytest). For example: [./development/lyxserver/server_monitor.c:173]: (error) Memory leak: pipename This had the obvious solution of adding free(pipename) to line 173. Convincing myself that this

Reporting bugs on the devel-list.

On Thu, Feb 25, 2010 at 12:24 AM, LyX Ticket Tracker wrote: > #6553: Assert on Opening the Edit menu to the left of a Math Inset >  PS. Why don't you report this on the devel-list. Especially if it concerns >  on-going business. The literal answer to your question is "because the bugtracker seem

Re: #6558: Edit->Language lacks keyboard shortcuts.

On Wed, Feb 24, 2010 at 10:08 PM, LyX Ticket Tracker wrote: > #6558: Edit->Language lacks keyboard shortcuts. >  I implemented a simpler solution (ignoring the casing) at r33555. > Ticket URL: OK, but adding a couple of lines of code makes this mu

Re: r33474 - in lyx-devel/trunk/src: . frontends/qt4

Pavel Sanda wrote: > so ok, what about when the 'run' version launches compare dialog, but starts > comparison immediately? but then Abdels vision of lyx -compare 437 444 file.lyx is not possible :( pavel

Re: r33474 - in lyx-devel/trunk/src: . frontends/qt4

Vincent van Ravesteijn - TNW wrote: > >> >maybe some panel like "[x] Skip internal VCS handling" and let user > >> >define check/in-out, log history in edit fields. problems - > >> > >> >there is no way how to define lyxvc().inUse, > >> > >> Why not ? > > > >if you want to introduce support for

RE: r33474 - in lyx-devel/trunk/src: . frontends/qt4

>> I meant, why do you want to retrieve the revision number of the >> current file, which you use in the call to svn cat. I guess that if >> you call svn cat without a revision number, it will get the last version. Or not ? > >but we want much more than the last version. inside we always call sv

Re: r33474 - in lyx-devel/trunk/src: . frontends/qt4

Abdelrazak Younes wrote: but we want much more than the last version. >>> >>> I am not sure we really want that actually... at least I am not sure... >>> I'd >>> rather rely on svn or Tortoisesvn ui capabilities and diff scripting >>> instead. >> >> tortoise is not limited to windows? > > Und

Re: r33474 - in lyx-devel/trunk/src: . frontends/qt4

On 02/24/2010 09:33 AM, Pavel Sanda wrote: Abdelrazak Younes wrote: but we want much more than the last version. I am not sure we really want that actually... at least I am not sure... I'd rather rely on svn or Tortoisesvn ui capabilities and diff scripting instead. tortoise is not limited t

Re: r33474 - in lyx-devel/trunk/src: . frontends/qt4

Abdelrazak Younes wrote: >> but we want much more than the last version. > > I am not sure we really want that actually... at least I am not sure... I'd > rather rely on svn or Tortoisesvn ui capabilities and diff scripting > instead. tortoise is not limited to windows? > What we really need is

Re: r33474 - in lyx-devel/trunk/src: . frontends/qt4

On 02/24/2010 04:55 AM, Pavel Sanda wrote: Vincent van Ravesteijn - TNW wrote: Why do you need the revision number for revision 0 ? the idea was that user would be able to address revisions not only by absolute revision number but also in relative manner, ie to let him ad