Am 25.10.2010 um 23:14 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Am 25.10.2010 um 22:01 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
The patch is ready and attached.
I tested all CVS functions and it works here.
>>>
>>> looks fine.
>>
>> Thanks.
>>
>>> the documentation of cou
On Mon, Oct 25, 2010 at 3:55 PM, Jürgen Spitzmüller wrote:
> Please let me know of other issues. Note particularly that all fixes that
> entail a string change should go in very soon, since we will turn to string
> freeze soon.
Well this string change doesn't affect branch, but I think we should
On Tue, Oct 26, 2010 at 5:22 AM, Pavel Sanda wrote:
> Richard Heck wrote:
I think we should just keep the
emergency file (unless it is obsolete).
>>> 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
In order to fix http://www.lyx.org/trac/ticket/6585 I need to check in InsetTabular if the table is
inside a float.
i thought I can do this by iterating the insets starting with the table inset down to the outer
insets. if one of the outer insets is a float I thought that I can say that the tab
On Mon, Oct 25, 2010 at 07:43:54PM +0200, Vincent van Ravesteijn wrote:
> > 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.
On Mon, Oct 25, 2010 at 03:49:33PM +0200, Abdelrazak Younes wrote:
> Well, most of the controller code was useless indirection and
> complication (most of the controller code was necessitating almost
> the same amount of code in the gui implementation). So I am ready to
> bet that, at feature equal
On Mon, Oct 25, 2010 at 07:51:04AM -0400, Richard Heck wrote:
> I could be wrong, but I think we now have much more application
> logic in the Gui* classes then we did before the removal of all the
> Controller* classes. Perhaps alot of that could just be copied over,
> but it is still more work.
Richard Heck wrote:
>>> - if (!Alert::prompt(_("Delete emergency file?"), str, 1,
>>> 1,
>>> - _("&Remove"), _("&Keep it"))) {
>>> - ...
>>>
>>> I think we should just keep the
>>> emergency file (unless it is obsolete).
>>>
>> no, i dont
Stephan Witt wrote:
> Am 25.10.2010 um 22:01 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> The patch is ready and attached.
> >> I tested all CVS functions and it works here.
> >
> > looks fine.
>
> Thanks.
>
> > the documentation of course ;)
>
> Sorry, I don't understand you.
> You mea
> 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
On 10/25/2010 04:22 PM, Pavel Sanda wrote:
John McCabe-Dansted wrote:
- if (!Alert::prompt(_("Delete emergency file?"), str, 1,
1,
- _("&Remove"), _("&Keep it"))) {
- ...
I think we should just keep the
emergency file (unless it
Am 25.10.2010 um 22:01 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> The patch is ready and attached.
>> I tested all CVS functions and it works here.
>
> looks fine.
Thanks.
> the documentation of course ;)
Sorry, I don't understand you.
You mean after writing the documentation I should backp
On 2010-10-25, Richard Heck wrote:
> On 10/25/2010 01:23 PM, John McCabe-Dansted wrote:
>> On Tue, Oct 26, 2010 at 12:03 AM, Richard Heck wrote:
+e.checksum() != s.checksum()) {
There are a number of ways to get a dirty buffer without actually
changing the
John McCabe-Dansted wrote:
> - if (!Alert::prompt(_("Delete emergency file?"), str, 1,
> 1,
> - _("&Remove"), _("&Keep it"))) {
> - ...
>
> I think we should just keep the
> emergency file (unless it is obsolete).
no, i dont agree here. i
Stephan Witt wrote:
> The patch is ready and attached.
> I tested all CVS functions and it works here.
looks fine. the documentation of course ;)
pavel
> > - compiler update
> > - boost update to 1.44
There's a typo in the log message (1.43),
but it IS boost 1.44.
Peter
Am Montag, den 25.10.2010, 20:30 +0200 schrieb Peter Kümmel:
> Am Montag, den 25.10.2010, 14:33 +0200 schrieb Pavel Sanda:
> > Most probably Peter,
> >
> > is there some way how to get rid of this:
>
> maybe
> - compiler update
> - boost update to 1.44
I've updated boost. (Updating boost was ne
Am Montag, den 25.10.2010, 14:33 +0200 schrieb Pavel Sanda:
> Most probably Peter,
>
> is there some way how to get rid of this:
maybe
- compiler update
- boost update to 1.44
- using Qt signals
- suppressing the warning -Wno-ignored-qualifiers
> CXXForkedCalls.o
> /usr/lib/gcc/i686-pc
On 10/25/2010 12:42 PM, Klaus-Peter Reimers wrote:
Moin from Kiel, Germany !
I installed lyx 1.6.7 from sources on an UBUNTU 10.4, which had 1.6.5
already installed, configured --with-version-suffix. When importing a
large bunch of LaTeX-sources into 1.6.7 indirectly (the construction is a.
litt
On 10/25/2010 01:23 PM, John McCabe-Dansted wrote:
On Tue, Oct 26, 2010 at 12:03 AM, Richard Heck wrote:
I think this was added a while ago, because we were leaving emergency files
lying around. We only ask about this if an attempt to recover the file has
been made, either successfully or n
Am 25.10.2010 um 16:53 schrieb Jürgen Spitzmüller:
> Stephan Witt wrote:
>> I'd like to prepare a backport of the CVS backend changes to make it usable
>> in 1.6.8. The dialog part of the changes I would skip so the other
>> backends are not modified.
>> May I do that or is it too late?
>
> If y
> 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.
>
>
I agree with John, having had the exact same problem. Rather than deleting
emergency files, they should be copied to a /tmp folder somewhere. This is
what vim does, and there's no reason not to do it in lyx.
Oh, and the autosave that goes down to 1 min only may be too little. I'd let
the user autos
Having lost a few mins of inspired writing, I'm all for leaving the
emergency files lying around...
Best,
-Jose
Jose Quesada, PhD.
Research scientist,
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada
On Mon, Oct 25,
On Tue, Oct 26, 2010 at 12:03 AM, Richard Heck wrote:
> I think this was added a while ago, because we were leaving emergency files
> lying around. We only ask about this if an attempt to recover the file has
> been made, either successfully or not. So either the document is now loaded
> in the bu
On Oct 25, 2010, at 4:51 AM, Richard Heck wrote:
> On 10/25/2010 03:52 AM, Abdelrazak Younes wrote:
>> On 10/24/2010 07:53 PM, Richard Heck wrote:
>>> On 10/24/2010 12:31 PM, David Whetstone wrote:
Hi, I'm new here. I only recently joined this list. I've recently
acquired an iPad, and
On Sun, Oct 24, 2010 at 11:01:53PM +0200, Vincent van Ravesteijn wrote:
> > I took a look and this looks good so far and a bit simpler than what I
> > thought would be necessary but I haven't tried to test it yet.
> >
>
> Please test if you have time. It was a long time ago for me too that I
> wor
Moin from Kiel, Germany !
I installed lyx 1.6.7 from sources on an UBUNTU 10.4, which had 1.6.5
already installed, configured --with-version-suffix. When importing a
large bunch of LaTeX-sources into 1.6.7 indirectly (the construction is a.
little bit tricky, hard to be explained and unnecessary t
Committed.
Vincent
On 10/25/2010 03:58 AM, John McCabe-Dansted wrote:
-
- if (!Alert::prompt(_("Delete emergency file?"), str, 1,
1,
- _("&Remove"), _("&K
On Mon, Oct 25, 2010 at 11:48 PM, Richard Heck wrote:
> As John said, it looks to me as if we remove the autosave file at the wrong
> time: What if the attempt to read the original file fails? It seems to me
> that we should remove it (a) if we read it successfully; (b) if we read the
> original s
When my file is modified externally and I select
File->Revert to Saved
I get the following warning.
"Any changes will be lost. Are you sure you want to revert to the
saved version
of the document ..."
I get this warning even when the buffer is clean so there are no
changes to be lost. I woul
So with Vincent's cleanup, we now have:
Buffer::ReadStatus Buffer::readAutosave(FileName const & fn)
{
// Now check if autosave file is newer.
FileName const autosaveFile = getAutosaveFileNameFor(fn);
if (!autosaveFile.exists()
|| autosaveFile.lastModified() <= fn.lastModif
Stephan Witt wrote:
> I'd like to prepare a backport of the CVS backend changes to make it usable
> in 1.6.8. The dialog part of the changes I would skip so the other
> backends are not modified.
> May I do that or is it too late?
If you are very fast and if the changes are safe. In general, I'd
Stephan Witt wrote:
> Am 25.10.2010 um 14:45 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> Patch is attached. Ok to apply?
> >
> > please go on.
>
> Done. (r35828)
>
> I'd like to prepare a backport of the CVS backend changes to make it usable
> in 1.6.8.
> The dialog part of the changes
On 10/25/2010 01:51 PM, Richard Heck wrote:
On 10/25/2010 03:52 AM, Abdelrazak Younes wrote:
On 10/24/2010 07:53 PM, Richard Heck wrote:
On 10/24/2010 12:31 PM, David Whetstone wrote:
Hi, I'm new here. I only recently joined this list. I've recently
acquired an iPad, and found myself wanting
Buffer.cpp:889: error: no 'lyx::Buffer::ReadStatus
lyx::Buffer::parseLyXFormat(lyx::Lexer&, const lyx::support::FileName&, int&)
const' member function declared in class 'lyx::Buffer'
Buffer.cpp: In member function 'lyx::Buffer::ReadStatus
lyx::Buffer::readFile(lyx::Lexer&, const lyx::support::F
Am 25.10.2010 um 14:45 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Patch is attached. Ok to apply?
>
> please go on.
Done. (r35828)
I'd like to prepare a backport of the CVS backend changes to make it usable in
1.6.8.
The dialog part of the changes I would skip so the other backends are not
Pavel Sanda wrote:
> my idea was that once both beta and 1.6.8 are out i would send mail to doc
> lists and cc all .po maintainers that its time to focus on 2.0 translation.
> secondly to ask you to become more strict for backporting any stuff so the
> possibility of introducing new regression in b
Jürgen Spitzmüller wrote:
> Pavel, do you still have plans for a coordinated beta/branch release?
i'm basically happy that 1.6.8 is going soon (without some particular
arrangements).
my idea was that once both beta and 1.6.8 are out i would send mail to doc
lists and cc all .po maintainers that
Stephan Witt wrote:
> Patch is attached. Ok to apply?
please go on.
pavel
Most probably Peter,
is there some way how to get rid of this:
CXXForkedCalls.o
/usr/lib/gcc/i686-pc-linux-gnu/4.3.2/include/g++-v4/tr1_impl/functional: In
static member function 'static void
boost::detail::function::void_function_obj_invoker2::invoke(boost::detail::function::function_bu
On 10/25/2010 07:57 AM, v...@lyx.org wrote:
Author: vfr
Date: Mon Oct 25 13:57:56 2010
New Revision: 35819
URL: http://www.lyx.org/trac/changeset/35819
Log:
Refactor Buffer.cpp: loadLyXFile():
...
- add more ReadStatus elements to describe failures.
I get several warnings now about value
On 10/25/2010 04:22 AM, John McCabe-Dansted wrote:
As discussed in trac [1] naming lyx files .lyx14 makes them hard to
open in LyX. Richard suggested instead naming them .14.lyx [1], and
targeted this to 2.0.0, however this has not been touched since then.
This has a simple patch against configur
Am 25.10.2010 um 13:02 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Or I can go to rcs and you'll do the svn implementation?
>
> i came to the conclusion that its less energy spent when i write the patch
> myself
> than doing detailed review and flame about nitpicks.
Ok. I finished the part2 o
On 10/25/2010 03:52 AM, Abdelrazak Younes wrote:
On 10/24/2010 07:53 PM, Richard Heck wrote:
On 10/24/2010 12:31 PM, David Whetstone wrote:
Hi, I'm new here. I only recently joined this list. I've recently
acquired an iPad, and found myself wanting to be able to take notes
with embedded equa
Stephan Witt wrote:
> Or I can go to rcs and you'll do the svn implementation?
i came to the conclusion that its less energy spent when i write the patch
myself
than doing detailed review and flame about nitpicks.
please make documentation for the current cvs state inside additional manual
and i
As discussed in trac [1] naming lyx files .lyx14 makes them hard to
open in LyX. Richard suggested instead naming them .14.lyx [1], and
targeted this to 2.0.0, however this has not been touched since then.
This has a simple patch against configure.py that I have been using on
Linux for months witho
I've been using a number of changes to Buffer::readFileHelper that
I've found useful. I err on the side off not delete emergency files,
and also add a Recover All option that is useful when you have a
master document that has several modified child documents.
I think that these modifications requi
This is just to let you know that I *do* have plans wrt LyX 1.6.8 :-)
I think another release is due. We have collected a range of fixes, including
some important ones (the misdetection of pLaTeX with TeXLive 2010, and of
course the crashes).
I see only two issues that should be sorted out befo
On 10/24/2010 07:53 PM, Richard Heck wrote:
On 10/24/2010 12:31 PM, David Whetstone wrote:
Hi, I'm new here. I only recently joined this list. I've recently
acquired an iPad, and found myself wanting to be able to take notes
with embedded equations and such. AFAICT, no such app yet exists.
Vincent van Ravesteijn wrote:
> I committed what works for me. I had it in my tree anyway.
i suspected something like that, thanks
ed.
52 matches
Mail list logo
