Re: #10781: LyX crash while moving between two open LyX files (I presume) -- report attached

[typist]

Ok; no problem. Thank you.
> On 12 Feb 2018, at 5:43 pm, LyX Ticket Tracker  wrote:
> 
> #10781: LyX crash while moving between two open LyX files (I presume) -- 
> report
> attached
> --+-
> Reporter:  lyx101|   Owner:  lasgouttes
> Type:  defect|  Status:  closed
> Priority:  high  |   Milestone:
> Component:  general   | Version:  2.2.3
> Severity:  critical  |  Resolution:  worksforme
> Keywords:  crash |
> --+-
> Changes (by spitz):
> 
> * status:  new => closed
> * resolution:   => worksforme
> 
> 
> Comment:
> 
> I propose to close this, then. lyx101, if you face the bug again after you
> entered heavy user mode, please reopen this ticket.
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

Re: Plan for final steps of 2.3.0 release

[José Abílio Matos]

On Saturday, 10 February 2018 18.51.44 WET Scott Kostyshak wrote:
> What is your feeling on how stable our 2.3.x branch currently is? I have
> the feeling that it is quite stable and that we should now make plans
> for the next step in the release process. I propose to make the final
> 2.3.0 release in about two weeks. What are your thoughts? Should we make
> a rc3 release? Should we wait longer than two weeks?

I have been using the 2.3 branch successfully and it is quite stable. 
Ironically just as Jürgen 
mentioned some of the bugs that I found, and that have been fixed, are bugs 
that have been 
here for a long time. :-)

So I too support a quick release with a fast 2.3.1 if the need arrives.

Another option would be to release an rc3 and after some time release that as 
the final 
version and rename it 2.3.0. At the moment I do not see any reason to justify 
this delay/
precaution that at the same time means more work.

Regards,
-- 
José Abílio

Re: Plan for final steps of 2.3.0 release

[Richard Heck]

On 02/10/2018 01:51 PM, Scott Kostyshak wrote:
> What is your feeling on how stable our 2.3.x branch currently is? I have the 
> feeling that it is quite stable and that we should now make plans for the 
> next step in the release process. I propose to make the final 2.3.0 release 
> in about two weeks. What are your thoughts? Should we make a rc3 release? 
> Should we wait longer than two weeks?

I have been using 2.3.x for regular work for a few months now, because I
needed some of the new features. I've had no problems with it at all.

I am also in favor of going ahead with the release. As JMarc said, we
can release 2.3.1 quickly if need be.

Richard

Re: #10781: LyX crash while moving between two open LyX files (I presume) -- report attached

[typist]

No, I have not seen this crash since my report. BUT I’ve not been a heavy user 
since that time. That will start again next month.

> On 12 Feb 2018, at 3:06 am, LyX Ticket Tracker  wrote:
> 
> #10781: LyX crash while moving between two open LyX files (I presume) -- 
> report
> attached
> --+-
> Reporter:  lyx101|   Owner:  lasgouttes
> Type:  defect|  Status:  new
> Priority:  high  |   Milestone:
> Component:  general   | Version:  2.2.3
> Severity:  critical  |  Resolution:
> Keywords:  crash |
> --+-
> 
> Comment (by skostysh):
> 
> Replying to [comment:1 skostysh]:
>> Can you reproduce the crash? If so, can you provide steps to reproduce
> it?
> 
> lyx101 do you still see this crash?
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

Re: Basque translation

[Kornel Benko]

Am Sonntag, 11. Februar 2018 18:12:25 CET schrieb Iñaki Larrañaga Murgoitio 
:
> Hi there,
> 
> Attached to this mail, you could find Basque translation for LyX.
> 
> Hope it’s not too late. Could you add it to LyX?
> 
> Thanks,
> 
> Dooteo

Without attachement? Too hard to process ...

Kornel

Basque translation

[Iñaki Larrañaga Murgoitio]

Hi there,

Attached to this mail, you could find Basque translation for LyX.

Hope it’s not too late. Could you add it to LyX?

Thanks, 

Dooteo

Re: Should child docs inherit trust for needauth converter?

[Scott Kostyshak]

On Sun, Feb 11, 2018 at 11:51:47AM +, Tommaso Cucinotta wrote:

> +1, from my viewpoint, perhaps we might have a TT tracking this request.

Done:

  https://www.lyx.org/trac/ticket/11031


signature.asc
Description: PGP signature

Re: [LyX/2.3.x] biblatex-natbib.citeengine: Remove erroneous blank

[Scott Kostyshak]

On Sun, Feb 11, 2018 at 04:06:27PM +, Jürgen Spitzmüller wrote:
> Am Sonntag, den 11.02.2018, 16:45 +0100 schrieb Juergen Spitzmueller:
> > commit 6c455707fe39a28edab8631d6ff973969b368bb1
> > Author: Juergen Spitzmueller
> > Date:   Sun Feb 11 16:43:14 2018 +0100
> > 
> > biblatex-natbib.citeengine: Remove erroneous blank
> 
> Scott, I took the liberty to commit this without talking back, since it
> is less than trivial.

That's fine, thanks.

Scott


signature.asc
Description: PGP signature

Re: [LyX/2.3.x] biblatex-natbib.citeengine: Remove erroneous blank

[Jürgen Spitzmüller]

Am Sonntag, den 11.02.2018, 16:45 +0100 schrieb Juergen Spitzmueller:
> commit 6c455707fe39a28edab8631d6ff973969b368bb1
> Author: Juergen Spitzmueller
> Date:   Sun Feb 11 16:43:14 2018 +0100
> 
> biblatex-natbib.citeengine: Remove erroneous blank

Scott, I took the liberty to commit this without talking back, since it
is less than trivial.

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Should child docs inherit trust for needauth converter?

[Tommaso Cucinotta]

On 02/01/2018 17:13, Jean-Marc Lasgouttes wrote:

Le 28/12/2017 à 09:40, Scott Kostyshak a écrit :

I suppose in cases of security, unless I can make a sound-proof argument
to get rid of the additional prompts, we should just keep them.

Any thoughts?


I would say that, if we trust the parent, we trust the child.


+1, from my viewpoint, perhaps we might have a TT tracking this request.

There's a few weirdnesses about editing:
1) I edit a doc, I say I trust it
2) later, I receive a contribution, save it locally
3) I include the contribution as a child, now what shall we do ?

Can't remember whether in LyX a child knows who else is including it
... instead, I guess/hope there's an easy function to go through all the
children of a doc ?

Thanks,

T.