Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie x...@yihui.name wrote:
 I'm pretty busy at the moment. I'm wondering if Scott can do it.

Sure, I can do that this weekend. Should it be done for both branch and trunk?

Scott

 Regards,
 Yihui
 --
 Yihui Xie xieyi...@gmail.com
 Phone: 515-294-2465 Web: http://yihui.name
 Department of Statistics, Iowa State University
 2215 Snedecor Hall, Ames, IA


 On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda sa...@lyx.org wrote:
 Kayvan Sylvan wrote:
 So I fixed the documentation (patch attached) and I now have a perfectly
 working solution for using LyX and noweb for literate programming.

 Please apply my patch and we can just close ticket 5444.

 Note that the Customization.lyx file had Change Tracking enabled, so I left
 it on. Someone will have to accept the changes after applying this patch.

 It is now in.
 BTW we still do not have a word about knitr in Additional manual.
 Yihui, what about add few paragraphs there?

 Pavel

Re: Re: Subject: [PATCH] Make text selectable in Help About LyX Version

[Scott Kostyshak]

On Tue, Oct 9, 2012 at 3:51 PM, Kornel Benko kor...@lyx.org wrote:
 Am Dienstag, 9. Oktober 2012 um 13:05:26, schrieb Scott Kostyshak
 skost...@lyx.org

 On Mon, Oct 8, 2012 at 7:41 PM, Pavel Sanda sa...@lyx.org wrote:

  Vincent van Ravesteijn wrote:

  Op 8-10-2012 21:07, Pavel Sanda schreef:

  Vincent van Ravesteijn wrote:

  I would prefer to have this tab only visible when DEVEL_VERSION is
  set.

  This doesn't provide much help in the released version.

  Multiple times we had bug reports where users were not able report Qt
  libs

  used.

  IIRC this was readable from the tab and would be useful... Pavel

 

  Qt libs are already in the normal Version tab (in the DEVEL_VERSION),
  but

 

  Oh, I see.



 In cmake this is the (boolean) variable LYX_DEVEL_VERSION, but it was not
 resolved to c++-define DEVEL_VERSION

 (Setting it had no effect whatsoever)



  do not appear in the new tab.

 

  Here they are (but perhaps cmake vs autotools difference).

 

  Pave



 Is there a consensus on what should be done here?



 Scott



 I corrected it now. Configuring whitt -DLYX_DEVEL_VERSION=ON has the same
 effect as

 configuring with configure ... --enable-build-type=dev ...



 Kornel

I'm still not sure what should be done here. I don't see the point of
having it for developers only -- can't developers always just run
--version? Maybe having it available in the build info tab is more
convenient for some?

I thought the idea was to get better bug reports from users. But it
seems that the extra information isn't that useful for bug reports
because most users install from binaries (for which we already know
the build information).

Thanks,

Scott

a bind works on Ubuntu but not on Windows

[Scott Kostyshak]

Regarding ticket http://www.lyx.org/trac/ticket/8364,

the following bind does not work for Michael (on Windows?):
\bind S-C-parenleft math-delim ( )

It does work for me on Ubuntu.

Michael found that the following does work
\bind S-C-9 math-delim ( )

but JMarc pointed out that this is not the right solution because it's
only for US keyboards and suggested
\bind ~S-C-parenleft math-delim ( )

This also works for me on Ubuntu, but not for Michael.

Why do the two parenleft binds work on Ubuntu and not on Windows?

Thanks,

Scott

Re: [PATCH] LFUN_BUFFER_FORALL

[Scott Kostyshak]

On Mon, Aug 27, 2012 at 12:09 PM, Scott Kostyshak
skost...@princeton.edu wrote:
 From: Jean-Marc Lasgouttes [lasgout...@lyx.org]
 Sent: Thursday, August 23, 2012 9:15 AM

Then I propose to simplify things a lot by only dispatching to visible
buffers (for now). No more special parameter.

 The updated patch is attached.

 How does it look?

 Scott

Any comments on this?

Thanks,

Scott

Re: [LyX master] Correctly initialize bool. Thanks, Pavel.

[Jürgen Spitzmüller]

This needs to go to branch as well.

Jürgen

2012/10/11 Juergen Spitzmueller sp...@lyx.org:
 The branch, master, has been updated.

 - Log -

 commit 47673f560f9af793f978482cef133b032fdb8692
 Author: Juergen Spitzmueller sp...@lyx.org
 Date:   Thu Oct 11 12:55:43 2012 +0200

 Correctly initialize bool. Thanks, Pavel.

 diff --git a/src/LaTeX.cpp b/src/LaTeX.cpp
 index b024f77..c9d3247 100644
 --- a/src/LaTeX.cpp
 +++ b/src/LaTeX.cpp
 @@ -94,7 +94,7 @@ bool operator!=(AuxInfo const  a, AuxInfo const  o)

  LaTeX::LaTeX(string const  latex, OutputParams const  rp,
  FileName const  f, string const  p)
 -   : cmd(latex), file(f), path(p), runparams(rp)
 +   : cmd(latex), file(f), path(p), runparams(rp), biber(false)
  {
 num_errors = 0;
 if (prefixIs(cmd, pdf)) { // Do we use pdflatex ?

 ---

 Summary of changes:
  src/LaTeX.cpp |2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)


 hooks/post-receive
 --
 The LyX Source Repository

Re: Re: Subject: [PATCH] Make text selectable in Help About LyX Version

[Liviu Andronic]

On Thu, Oct 11, 2012 at 12:46 PM, Scott Kostyshak skost...@lyx.org wrote:
 I thought the idea was to get better bug reports from users. But it
 seems that the extra information isn't that useful for bug reports

 because most users install from binaries (for which we already know
 the build information).

Not necessarily. There are a myriad Linux distributions and for each
bug report the user/devel are unlikely to check the packaging habits
of the given distro.

My 00.02€
Liviu

Re: Re: Subject: [PATCH] Make text selectable in Help About LyX Version

[Scott Kostyshak]

On Thu, Oct 11, 2012 at 8:17 AM, Liviu Andronic landronim...@gmail.com wrote:
 On Thu, Oct 11, 2012 at 12:46 PM, Scott Kostyshak skost...@lyx.org wrote:
 I thought the idea was to get better bug reports from users. But it
 seems that the extra information isn't that useful for bug reports

 because most users install from binaries (for which we already know
 the build information).

 Not necessarily. There are a myriad Linux distributions and for each
 bug report the user/devel are unlikely to check the packaging habits
 of the given distro.

Good point. But if someone is on Linux they are probably comfortable
doing --version. That's not true for everyone though. I know people
who use Linux and are still terrified by the terminal.

Scott

 My 00.02€
 Liviu

Re: #8372: PDF-graphics import to LyX document

[Gerry Danilatos]

Tremendous!!!

The alternate installer works perfectly. Problem solved.

Thank you very much, indeed.

GerryD
--

On Thu, Oct 11, 2012 at 9:38 PM, LyX Ticket Tracker t...@lyx.org wrote:

 #8372: PDF-graphics import to LyX document
 +
  Reporter:  gerryD  |   Owner:  uwestoehr
  Type:  defect  |  Status:  assigned
  Priority:  normal  |   Milestone:
 Component:  convertors  | Version:  2.0.4
  Severity:  normal  |  Resolution:
  Keywords:  |
 +
 Changes (by spitz):

  * owner:  GerryD = uwestoehr
  * status:  new = assigned


 --
 Ticket URL: http://www.lyx.org/trac/ticket/8372#comment:2
 The LyX Project http://www.lyx.org/
 LyX -- The Document Processor

Re: LyX functions for bibliography managers

[Benjamin Piwowarski]

Hi,

I decomposed the patch in 5 steps:

1) Refactored BibTeX parsing (InsetBibtex)
2) Add a method to update a BibTeX file (InsetBibtex and BiblioInfo)
3) Detection and status cache of BibTeX managed files (InsetBibtex, Buffer)
4) Method to add a set of keys to InsetCitation (InsetCitation)
5) Add bibtex-insert LFUN (LyxAction, BufferView, FuncCode)

I added to the TRAC ticket a new attachement (bibtex-insert-000.2.patch) that 
shows all the steps. Please note that in the TRAC web interface, you can search 
for [PATCH to go from one patch to the other.

Benjamin


On Oct 10, 2012, at 16:30 , Richard Heck rgh...@lyx.org wrote:

 On 10/10/2012 09:41 AM, Benjamin Piwowarski wrote:
 Hi,
 
 I created a patch implementing the bibtex-insert function, please see
 
 http://www.lyx.org/trac/ticket/8368
 
 [snip]
 
 The patch basically refactored the code that was used to parse a BibTeX file 
 (in InsetBibtex.cpp), so it can be used to parse the managed file without 
 updating any buffer cache, in order to update the BibTeX file. I also 
 changed the information stored for each bibtex file in order to store the 
 last update timestamp as well as the managed flag.
 
 I'd suggest dividing the patch into pieces. The first one might simply 
 refactor the code a bit, then the next one (or two, or however many) add 
 additional pieces, one coherent unit at a time. This makes reading the 
 patches easier, and also allows any introduced bugs to be localized.
 
 Richard
 

--
Benjamin Piwowarski
LIP6/CNRS, University Pierre et Marie Curie (UPMC)
case 169 – 4, Place de Jussieu – 75252 Paris cedex 05 – France
benja...@bpiwowar.net
http://www.bpiwowar.net/

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
 On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie x...@yihui.name wrote:
  I'm pretty busy at the moment. I'm wondering if Scott can do it.
 
 Sure, I can do that this weekend. Should it be done for both branch and trunk?

Primarily for trunk, backport to branch would nice though. Pavel

Re: About LyX menus usability.

[Pavel Sanda]

Tommaso Cucinotta wrote:
 -) move Marginal note (and Footnote ?) to Insert-Note sub-menu


Knowing well that I'm opening pandora box and risking subsequent flames
when it comes to Insert menu we could 
a) hide not so often used entries somewhere
  - Date -?
  - Short Title - Float (I believe its to be used only with floats?)

b) group similar things together (based on your proposals)
  - Citation, Reference, Label, URL, Hyperlink are somewhat similar enough to 
be joined
(do you see the reason behind horizontal line after nomeclature?)
However I'm not sure about moving it to submenu as you proposed.
If you use crossref/label or citations often it could be PITA for many 
users ;)
  - Marginal  Foot - can also go to Note submenu.
But the same applies here as in point above - moving often used entries to 
submenu is not good idea.
So I would be rather careful what other people think about it.

Pavel

Re: About LyX menus usability.

[Liviu Andronic]

On Thu, Oct 11, 2012 at 5:33 PM, Pavel Sanda sa...@lyx.org wrote:
 Tommaso Cucinotta wrote:
 -) move Marginal note (and Footnote ?) to Insert-Note sub-menu
 

 Knowing well that I'm opening pandora box and risking subsequent flames
 when it comes to Insert menu we could
 a) hide not so often used entries somewhere
   - Date -?
   - Short Title - Float (I believe its to be used only with floats?)


 b) group similar things together (based on your proposals)
   - Citation, Reference, Label, URL, Hyperlink are somewhat similar enough to 
 be joined

This makes sense to me.


 (do you see the reason behind horizontal line after nomeclature?)
 However I'm not sure about moving it to submenu as you proposed.
 If you use crossref/label or citations often it could be PITA for many 
 users ;)

If you really use this often, you're likely to use the toolbar buttons
instead of the menu.

Liviu


   - Marginal  Foot - can also go to Note submenu.
 But the same applies here as in point above - moving often used entries 
 to submenu is not good idea.
 So I would be rather careful what other people think about it.

 Pavel



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: LyX functions for bibliography managers

[Richard Heck]

On 10/11/2012 10:51 AM, Benjamin Piwowarski wrote:

Hi,

I decomposed the patch in 5 steps:

1) Refactored BibTeX parsing (InsetBibtex)
2) Add a method to update a BibTeX file (InsetBibtex and BiblioInfo)
3) Detection and status cache of BibTeX managed files (InsetBibtex, Buffer)
4) Method to add a set of keys to InsetCitation (InsetCitation)
5) Add bibtex-insert LFUN (LyxAction, BufferView, FuncCode)

I added to the TRAC ticket a new attachement (bibtex-insert-000.2.patch) that 
shows all the steps. Please note that in the TRAC web interface, you can search 
for [PATCH to go from one patch to the other.
OK, thanks very much. I'll have a look before too long, or else perhaps 
Julien can get to it. He's really the citation expert these days.


rh

Re: About LyX menus usability.

[Jürgen Spitzmüller]

2012/10/11 Pavel Sanda sa...@lyx.org:
 Tommaso Cucinotta wrote:
 -) move Marginal note (and Footnote ?) to Insert-Note sub-menu

Footnote to submenu? No please (this is a too important feature).

 Knowing well that I'm opening pandora box and risking subsequent flames
 when it comes to Insert menu we could
 a) hide not so often used entries somewhere
   - Date -?
   - Short Title - Float (I believe its to be used only with floats?)

Nope, short title is used whenever an optional argument is to be
inserted (e.g. in sections).

moving often used entries to submenu is not good idea.
 So I would be rather careful what other people think about it.

hear, hear.

Jürgen

 Pavel

Re: About LyX menus usability.

[Jürgen Spitzmüller]

2012/10/11 Liviu Andronic landronim...@gmail.com:
 (do you see the reason behind horizontal line after nomeclature?)
 However I'm not sure about moving it to submenu as you proposed.
 If you use crossref/label or citations often it could be PITA for many 
 users ;)

 If you really use this often, you're likely to use the toolbar buttons
 instead of the menu.

If I count as a counter-example: I use those very often, and I always
access them by menu, not toolbar. Submenu would be a PITA.

Jürgen

Re: Re: About LyX menus usability.

[Kornel Benko]

Am Donnerstag, 11. Oktober 2012 um 17:33:19, schrieb Pavel Sanda sa...@lyx.org
 Tommaso Cucinotta wrote:
  -) move Marginal note (and Footnote ?) to Insert-Note sub-menu
 
 
 Knowing well that I'm opening pandora box and risking subsequent flames
 when it comes to Insert menu we could 
 a) hide not so often used entries somewhere
   - Date -?

+1

   - Short Title - Float (I believe its to be used only with floats?)

-1
Used also as entry in table of content

 b) group similar things together (based on your proposals)
   - Citation, Reference, Label, URL, Hyperlink are somewhat similar enough to 
 be joined
 (do you see the reason behind horizontal line after nomeclature?)
 However I'm not sure about moving it to submenu as you proposed.
 If you use crossref/label or citations often it could be PITA for many 
 users ;)

+1

   - Marginal  Foot - can also go to Note submenu.
 But the same applies here as in point above - moving often used entries 
 to submenu is not good idea.
 So I would be rather careful what other people think about it.

At least, one can bind often used things to some key-sequence.

 Pavel

Kornel

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

Re: About LyX menus usability.

[Pavel Sanda]

Jürgen Spitzmüller wrote:
 moving often used entries to submenu is not good idea.
  So I would be rather careful what other people think about it.
 
 hear, hear.

Yes I expected something like this :)
Pavel

Re: a bind works on Ubuntu but not on Windows

[Jean-Marc Lasgouttes]

Le 11/10/12 12:50, Scott Kostyshak a écrit :

Regarding ticket http://www.lyx.org/trac/ticket/8364,

the following bind does not work for Michael (on Windows?):
\bind S-C-parenleft math-delim ( )

It does work for me on Ubuntu.

Michael found that the following does work
\bind S-C-9 math-delim ( )

but JMarc pointed out that this is not the right solution because it's
only for US keyboards and suggested
\bind ~S-C-parenleft math-delim ( )

This also works for me on Ubuntu, but not for Michael.

Why do the two parenleft binds work on Ubuntu and not on Windows?


I did not have time to look but the first thing to chck of course is 
whether the keyboard layouts are the same.


We do not want to use S-C-9 anyway because it would not work on a non-US 
keyboard.


But their may be a specific windows problem indeed.

JMarc

Re: Subject: [PATCH] Make text selectable in Help About LyX Version

[Jean-Marc Lasgouttes]

Le 11/10/12 12:46, Scott Kostyshak a écrit :

I'm still not sure what should be done here. I don't see the point of
having it for developers only -- can't developers always just run
--version? Maybe having it available in the build info tab is more
convenient for some?

I thought the idea was to get better bug reports from users. But it
seems that the extra information isn't that useful for bug reports
because most users install from binaries (for which we already know
the build information).


I thought it was a good idea too when I suggested it. Personnally I do 
not know what are the options used by uwe or Stephan when they compile.


And for linux distributions, many user are not comfortable with using 
--version IMO.


JMarc

PS: on a related not, how difficult/easy it is to have the git revision 
in there?

Re: About LyX menus usability.

[Jean-Marc Lasgouttes]

Le 11/10/12 17:42, Liviu Andronic a écrit :

 However I'm not sure about moving it to submenu as you proposed.
 If you use crossref/label or citations often it could be PITA for many 
users ;)


If you really use this often, you're likely to use the toolbar buttons
instead of the menu.


Keyboard shortcuts are more expensive in submenus.

Actually having a working ubuntu HUD would be nice here.

JMarc

Re: About LyX menus usability.

[Jean-Marc Lasgouttes]

Le 11/10/12 20:42, Pavel Sanda a écrit :

Jürgen Spitzmüller wrote:

moving often used entries to submenu is not good idea.
 So I would be rather careful what other people think about it.


hear, hear.


Yes I expected something like this :)


How difficult would it be to collect information to build a heat-map of 
the toolbar/menus?


JMarc

Re: Subject: [PATCH] Make text selectable in Help About LyX Version

[Vincent van Ravesteijn]

Op 11-10-2012 23:09, Jean-Marc Lasgouttes schreef:

Le 11/10/12 12:46, Scott Kostyshak a écrit :

I'm still not sure what should be done here. I don't see the point of
having it for developers only -- can't developers always just run
--version? Maybe having it available in the build info tab is more
convenient for some?

I thought the idea was to get better bug reports from users. But it
seems that the extra information isn't that useful for bug reports
because most users install from binaries (for which we already know
the build information).


I thought it was a good idea too when I suggested it. Personnally I do 
not know what are the options used by uwe or Stephan when they compile.


And for linux distributions, many user are not comfortable with using 
--version IMO.


My problem is that we have an extra tab with no additional information. 
Well, with CMake that is.


What useful information is there on Linux with autotools ? (except for 
Qt libs, because those are already in the normal version tab, if one 
removes the #ifdef DEVEL_VERSION).


Vincent

Re: Subject: [PATCH] Make text selectable in Help About LyX Version

[Liviu Andronic]

On Thu, Oct 11, 2012 at 11:20 PM, Vincent van Ravesteijn v...@lyx.org wrote:
 My problem is that we have an extra tab with no additional information.
 Well, with CMake that is.

 What useful information is there on Linux with autotools ? (except for Qt
 libs, because those are already in the normal version tab, if one removes
 the #ifdef DEVEL_VERSION).

LyX 2.1.0dev (2011-04-29)
Built on Oct 11 2012, 17:58:16
Configuration
  Host type:x86_64-pc-linux-gnu
  Special build flags:  build=release warnings use-aspell
use-enchant use-hunspell
  C   Compiler: gcc
  C   Compiler LyX flags:
  C   Compiler flags:   -D_FORTIFY_SOURCE=2 -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
  C++ Compiler: g++ (4.6)
  C++ Compiler LyX flags:
  C++ Compiler flags:   -D_FORTIFY_SOURCE=2 -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
  Linker flags:
  Linker user flags:-Wl,-Bsymbolic-functions -Wl,-z,relro
-Wl,-z,defs -Wl,--as-needed -Wl,-z,defs -Wl,--as-needed
  Qt 4 Frontend:
  Qt 4 version: 4.8.1
  Packaging:posix
  LyX binary dir:   /usr/bin
  LyX files dir:/usr/share/lyx2.1


Personally I find the build date very useful and, as JMarc suggested,
it would be nice to have the GIT revision there, too. All in all this
new tab is useful for reporting bugs.

Liviu

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie  wrote:
> I'm pretty busy at the moment. I'm wondering if Scott can do it.

Sure, I can do that this weekend. Should it be done for both branch and trunk?

Scott

> Regards,
> Yihui
> --
> Yihui Xie 
> Phone: 515-294-2465 Web: http://yihui.name
> Department of Statistics, Iowa State University
> 2215 Snedecor Hall, Ames, IA
>
>
> On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda  wrote:
>> Kayvan Sylvan wrote:
>>> So I fixed the documentation (patch attached) and I now have a perfectly
>>> working solution for using LyX and noweb for literate programming.
>>>
>>> Please apply my patch and we can just close ticket 5444.
>>>
>>> Note that the Customization.lyx file had Change Tracking enabled, so I left
>>> it on. Someone will have to accept the changes after applying this patch.
>>
>> It is now in.
>> BTW we still do not have a word about knitr in Additional manual.
>> Yihui, what about add few paragraphs there?
>>
>> Pavel

Re: Re: Subject: [PATCH] Make text selectable in Help > About LyX > Version

[Scott Kostyshak]

On Tue, Oct 9, 2012 at 3:51 PM, Kornel Benko  wrote:
> Am Dienstag, 9. Oktober 2012 um 13:05:26, schrieb Scott Kostyshak
> 
>
>> On Mon, Oct 8, 2012 at 7:41 PM, Pavel Sanda  wrote:
>
>> > Vincent van Ravesteijn wrote:
>
>> >> Op 8-10-2012 21:07, Pavel Sanda schreef:
>
>> >>> Vincent van Ravesteijn wrote:
>
>>  I would prefer to have this tab only visible when DEVEL_VERSION is
>>  set.
>
>>  This doesn't provide much help in the released version.
>
>> >>> Multiple times we had bug reports where users were not able report Qt
>> >>> libs
>
>> >>> used.
>
>> >>> IIRC this was readable from the tab and would be useful... Pavel
>
>> >>
>
>> >> Qt libs are already in the normal "Version" tab (in the DEVEL_VERSION),
>> >> but
>
>> >
>
>> > Oh, I see.
>
>
>
> In cmake this is the (boolean) variable LYX_DEVEL_VERSION, but it was not
> resolved to c++-define DEVEL_VERSION
>
> (Setting it had no effect whatsoever)
>
>
>
>> >> do not appear in the new tab.
>
>> >
>
>> > Here they are (but perhaps cmake vs autotools difference).
>
>> >
>
>> > Pave
>
>>
>
>> Is there a consensus on what should be done here?
>
>>
>
>> Scott
>
>
>
> I corrected it now. Configuring whitt -DLYX_DEVEL_VERSION=ON has the same
> effect as
>
> configuring with "configure ... --enable-build-type=dev ..."
>
>
>
> Kornel

I'm still not sure what should be done here. I don't see the point of
having it for developers only -- can't developers always just run
--version? Maybe having it available in the build info tab is more
convenient for some?

I thought the idea was to get better bug reports from users. But it
seems that the extra information isn't that useful for bug reports
because most users install from binaries (for which we already know
the build information).

Thanks,

Scott

a bind works on Ubuntu but not on Windows

[Scott Kostyshak]

Regarding ticket http://www.lyx.org/trac/ticket/8364,

the following bind does not work for Michael (on Windows?):
\bind "S-C-parenleft" "math-delim ( )"

It does work for me on Ubuntu.

Michael found that the following does work
\bind "S-C-9" "math-delim ( )"

but JMarc pointed out that this is not the right solution because it's
only for US keyboards and suggested
\bind "~S-C-parenleft" "math-delim ( )"

This also works for me on Ubuntu, but not for Michael.

Why do the two parenleft binds work on Ubuntu and not on Windows?

Thanks,

Scott

Re: [PATCH] LFUN_BUFFER_FORALL

[Scott Kostyshak]

On Mon, Aug 27, 2012 at 12:09 PM, Scott Kostyshak
 wrote:
> From: Jean-Marc Lasgouttes [lasgout...@lyx.org]
> Sent: Thursday, August 23, 2012 9:15 AM
>
>>Then I propose to simplify things a lot by only dispatching to visible
>>buffers (for now). No more special parameter.
>
> The updated patch is attached.
>
> How does it look?
>
> Scott

Any comments on this?

Thanks,

Scott

Re: [LyX master] Correctly initialize bool. Thanks, Pavel.

[Jürgen Spitzmüller]

This needs to go to branch as well.

Jürgen

2012/10/11 Juergen Spitzmueller :
> The branch, master, has been updated.
>
> - Log -
>
> commit 47673f560f9af793f978482cef133b032fdb8692
> Author: Juergen Spitzmueller 
> Date:   Thu Oct 11 12:55:43 2012 +0200
>
> Correctly initialize bool. Thanks, Pavel.
>
> diff --git a/src/LaTeX.cpp b/src/LaTeX.cpp
> index b024f77..c9d3247 100644
> --- a/src/LaTeX.cpp
> +++ b/src/LaTeX.cpp
> @@ -94,7 +94,7 @@ bool operator!=(AuxInfo const & a, AuxInfo const & o)
>
>  LaTeX::LaTeX(string const & latex, OutputParams const & rp,
>  FileName const & f, string const & p)
> -   : cmd(latex), file(f), path(p), runparams(rp)
> +   : cmd(latex), file(f), path(p), runparams(rp), biber(false)
>  {
> num_errors = 0;
> if (prefixIs(cmd, "pdf")) { // Do we use pdflatex ?
>
> ---
>
> Summary of changes:
>  src/LaTeX.cpp |2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
>
> hooks/post-receive
> --
> The LyX Source Repository

Re: Re: Subject: [PATCH] Make text selectable in Help > About LyX > Version

[Liviu Andronic]

On Thu, Oct 11, 2012 at 12:46 PM, Scott Kostyshak  wrote:
> I thought the idea was to get better bug reports from users. But it
> seems that the extra information isn't that useful for bug reports

> because most users install from binaries (for which we already know
> the build information).
>
Not necessarily. There are a myriad Linux distributions and for each
bug report the user/devel are unlikely to check the packaging habits
of the given distro.

My 00.02€
Liviu

Re: Re: Subject: [PATCH] Make text selectable in Help > About LyX > Version

[Scott Kostyshak]

On Thu, Oct 11, 2012 at 8:17 AM, Liviu Andronic  wrote:
> On Thu, Oct 11, 2012 at 12:46 PM, Scott Kostyshak  wrote:
>> I thought the idea was to get better bug reports from users. But it
>> seems that the extra information isn't that useful for bug reports
>
>> because most users install from binaries (for which we already know
>> the build information).
>>
> Not necessarily. There are a myriad Linux distributions and for each
> bug report the user/devel are unlikely to check the packaging habits
> of the given distro.

Good point. But if someone is on Linux they are probably comfortable
doing --version. That's not true for everyone though. I know people
who use Linux and are still terrified by the terminal.

Scott

> My 00.02€
> Liviu

Re: #8372: PDF-graphics import to LyX document

[Gerry Danilatos]

Tremendous!!!

The alternate installer works perfectly. Problem solved.

Thank you very much, indeed.

GerryD
--

On Thu, Oct 11, 2012 at 9:38 PM, LyX Ticket Tracker  wrote:

> #8372: PDF-graphics import to LyX document
> +
>  Reporter:  gerryD  |   Owner:  uwestoehr
>  Type:  defect  |  Status:  assigned
>  Priority:  normal  |   Milestone:
> Component:  convertors  | Version:  2.0.4
>  Severity:  normal  |  Resolution:
>  Keywords:  |
> +
> Changes (by spitz):
>
>  * owner:  GerryD => uwestoehr
>  * status:  new => assigned
>
>
> --
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor
>

Re: LyX functions for bibliography managers

[Benjamin Piwowarski]

Hi,

I decomposed the patch in 5 steps:

1) Refactored BibTeX parsing (InsetBibtex)
2) Add a method to update a BibTeX file (InsetBibtex and BiblioInfo)
3) Detection and status cache of BibTeX managed files (InsetBibtex, Buffer)
4) Method to add a set of keys to InsetCitation (InsetCitation)
5) Add bibtex-insert LFUN (LyxAction, BufferView, FuncCode)

I added to the TRAC ticket a new attachement (bibtex-insert-000.2.patch) that 
shows all the steps. Please note that in the TRAC web interface, you can search 
for [PATCH to go from one patch to the other.

Benjamin


On Oct 10, 2012, at 16:30 , Richard Heck  wrote:

> On 10/10/2012 09:41 AM, Benjamin Piwowarski wrote:
>> Hi,
>> 
>> I created a patch implementing the "bibtex-insert" function, please see
>> 
>> http://www.lyx.org/trac/ticket/8368
>> 
>> [snip]
>> 
>> The patch basically refactored the code that was used to parse a BibTeX file 
>> (in InsetBibtex.cpp), so it can be used to parse the managed file without 
>> updating any buffer cache, in order to update the BibTeX file. I also 
>> changed the information stored for each bibtex file in order to store the 
>> last update timestamp as well as the "managed" flag.
>> 
> I'd suggest dividing the patch into pieces. The first one might simply 
> refactor the code a bit, then the next one (or two, or however many) add 
> additional pieces, one coherent unit at a time. This makes reading the 
> patches easier, and also allows any introduced bugs to be localized.
> 
> Richard
> 

--
Benjamin Piwowarski
LIP6/CNRS, University Pierre et Marie Curie (UPMC)
case 169 – 4, Place de Jussieu – 75252 Paris cedex 05 – France
benja...@bpiwowar.net
http://www.bpiwowar.net/

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
> On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie  wrote:
> > I'm pretty busy at the moment. I'm wondering if Scott can do it.
> 
> Sure, I can do that this weekend. Should it be done for both branch and trunk?

Primarily for trunk, backport to branch would nice though. Pavel

Re: About LyX menus & usability.

[Pavel Sanda]

Tommaso Cucinotta wrote:
> -) move Marginal note (and Footnote ?) to Insert->Note sub-menu


Knowing well that I'm opening pandora box and risking subsequent flames
when it comes to Insert menu we could 
a) hide not so often used entries somewhere
  - Date ->?
  - Short Title -> Float (I believe its to be used only with floats?)

b) group similar things together (based on your proposals)
  - Citation, Reference, Label, URL, Hyperlink are somewhat similar enough to 
be joined
(do you see the reason behind horizontal line after nomeclature?)
However I'm not sure about moving it to submenu as you proposed.
If you use crossref/label or citations often it could be PITA for many 
users ;)
  - Marginal & Foot - can also go to Note submenu.
But the same applies here as in point above - moving often used entries to 
submenu is not good idea.
So I would be rather careful what other people think about it.

Pavel

Re: About LyX menus & usability.

[Liviu Andronic]

On Thu, Oct 11, 2012 at 5:33 PM, Pavel Sanda  wrote:
> Tommaso Cucinotta wrote:
>> -) move Marginal note (and Footnote ?) to Insert->Note sub-menu
> 
>
> Knowing well that I'm opening pandora box and risking subsequent flames
> when it comes to Insert menu we could
> a) hide not so often used entries somewhere
>   - Date ->?
>   - Short Title -> Float (I believe its to be used only with floats?)
>

> b) group similar things together (based on your proposals)
>   - Citation, Reference, Label, URL, Hyperlink are somewhat similar enough to 
> be joined
>
This makes sense to me.


> (do you see the reason behind horizontal line after nomeclature?)
> However I'm not sure about moving it to submenu as you proposed.
> If you use crossref/label or citations often it could be PITA for many 
> users ;)
>
If you really use this often, you're likely to use the toolbar buttons
instead of the menu.

Liviu


>   - Marginal & Foot - can also go to Note submenu.
> But the same applies here as in point above - moving often used entries 
> to submenu is not good idea.
> So I would be rather careful what other people think about it.
>
> Pavel



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: LyX functions for bibliography managers

[Richard Heck]

On 10/11/2012 10:51 AM, Benjamin Piwowarski wrote:

Hi,

I decomposed the patch in 5 steps:

1) Refactored BibTeX parsing (InsetBibtex)
2) Add a method to update a BibTeX file (InsetBibtex and BiblioInfo)
3) Detection and status cache of BibTeX managed files (InsetBibtex, Buffer)
4) Method to add a set of keys to InsetCitation (InsetCitation)
5) Add bibtex-insert LFUN (LyxAction, BufferView, FuncCode)

I added to the TRAC ticket a new attachement (bibtex-insert-000.2.patch) that 
shows all the steps. Please note that in the TRAC web interface, you can search 
for [PATCH to go from one patch to the other.
OK, thanks very much. I'll have a look before too long, or else perhaps 
Julien can get to it. He's really the citation expert these days.


rh

Re: About LyX menus & usability.

[Jürgen Spitzmüller]

2012/10/11 Pavel Sanda :
> Tommaso Cucinotta wrote:
>> -) move Marginal note (and Footnote ?) to Insert->Note sub-menu

Footnote to submenu? No please (this is a too important feature).

> Knowing well that I'm opening pandora box and risking subsequent flames
> when it comes to Insert menu we could
> a) hide not so often used entries somewhere
>   - Date ->?
>   - Short Title -> Float (I believe its to be used only with floats?)

Nope, short title is used whenever an optional argument is to be
inserted (e.g. in sections).

>moving often used entries to submenu is not good idea.
> So I would be rather careful what other people think about it.

hear, hear.

Jürgen

> Pavel

Re: About LyX menus & usability.

[Jürgen Spitzmüller]

2012/10/11 Liviu Andronic :
>> (do you see the reason behind horizontal line after nomeclature?)
>> However I'm not sure about moving it to submenu as you proposed.
>> If you use crossref/label or citations often it could be PITA for many 
>> users ;)
>>
> If you really use this often, you're likely to use the toolbar buttons
> instead of the menu.

If I count as a counter-example: I use those very often, and I always
access them by menu, not toolbar. Submenu would be a PITA.

Jürgen

Re: Re: About LyX menus & usability.

[Kornel Benko]

Am Donnerstag, 11. Oktober 2012 um 17:33:19, schrieb Pavel Sanda 
> Tommaso Cucinotta wrote:
> > -) move Marginal note (and Footnote ?) to Insert->Note sub-menu
> 
> 
> Knowing well that I'm opening pandora box and risking subsequent flames
> when it comes to Insert menu we could 
> a) hide not so often used entries somewhere
>   - Date ->?

+1

>   - Short Title -> Float (I believe its to be used only with floats?)

-1
Used also as entry in table of content

> b) group similar things together (based on your proposals)
>   - Citation, Reference, Label, URL, Hyperlink are somewhat similar enough to 
> be joined
> (do you see the reason behind horizontal line after nomeclature?)
> However I'm not sure about moving it to submenu as you proposed.
> If you use crossref/label or citations often it could be PITA for many 
> users ;)

+1

>   - Marginal & Foot - can also go to Note submenu.
> But the same applies here as in point above - moving often used entries 
> to submenu is not good idea.
> So I would be rather careful what other people think about it.

At least, one can bind often used things to some key-sequence.

> Pavel

Kornel

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

Re: About LyX menus & usability.

[Pavel Sanda]

Jürgen Spitzmüller wrote:
> >moving often used entries to submenu is not good idea.
> > So I would be rather careful what other people think about it.
> 
> hear, hear.

Yes I expected something like this :)
Pavel

Re: a bind works on Ubuntu but not on Windows

[Jean-Marc Lasgouttes]

Le 11/10/12 12:50, Scott Kostyshak a écrit :

Regarding ticket http://www.lyx.org/trac/ticket/8364,

the following bind does not work for Michael (on Windows?):
\bind "S-C-parenleft" "math-delim ( )"

It does work for me on Ubuntu.

Michael found that the following does work
\bind "S-C-9" "math-delim ( )"

but JMarc pointed out that this is not the right solution because it's
only for US keyboards and suggested
\bind "~S-C-parenleft" "math-delim ( )"

This also works for me on Ubuntu, but not for Michael.

Why do the two parenleft binds work on Ubuntu and not on Windows?


I did not have time to look but the first thing to chck of course is 
whether the keyboard layouts are the same.


We do not want to use S-C-9 anyway because it would not work on a non-US 
keyboard.


But their may be a specific windows problem indeed.

JMarc

Re: Subject: [PATCH] Make text selectable in Help > About LyX > Version

[Jean-Marc Lasgouttes]

Le 11/10/12 12:46, Scott Kostyshak a écrit :

I'm still not sure what should be done here. I don't see the point of
having it for developers only -- can't developers always just run
--version? Maybe having it available in the build info tab is more
convenient for some?

I thought the idea was to get better bug reports from users. But it
seems that the extra information isn't that useful for bug reports
because most users install from binaries (for which we already know
the build information).


I thought it was a good idea too when I suggested it. Personnally I do 
not know what are the options used by uwe or Stephan when they compile.


And for linux distributions, many user are not comfortable with using 
--version IMO.


JMarc

PS: on a related not, how difficult/easy it is to have the git revision 
in there?

Re: About LyX menus & usability.

[Jean-Marc Lasgouttes]

Le 11/10/12 17:42, Liviu Andronic a écrit :

 However I'm not sure about moving it to submenu as you proposed.
 If you use crossref/label or citations often it could be PITA for many 
users ;)


If you really use this often, you're likely to use the toolbar buttons
instead of the menu.


Keyboard shortcuts are more expensive in submenus.

Actually having a working ubuntu HUD would be nice here.

JMarc

Re: About LyX menus & usability.

[Jean-Marc Lasgouttes]

Le 11/10/12 20:42, Pavel Sanda a écrit :

Jürgen Spitzmüller wrote:

moving often used entries to submenu is not good idea.
 So I would be rather careful what other people think about it.


hear, hear.


Yes I expected something like this :)


How difficult would it be to collect information to build a heat-map of 
the toolbar/menus?


JMarc

Re: Subject: [PATCH] Make text selectable in Help > About LyX > Version

[Vincent van Ravesteijn]

Op 11-10-2012 23:09, Jean-Marc Lasgouttes schreef:

Le 11/10/12 12:46, Scott Kostyshak a écrit :

I'm still not sure what should be done here. I don't see the point of
having it for developers only -- can't developers always just run
--version? Maybe having it available in the build info tab is more
convenient for some?

I thought the idea was to get better bug reports from users. But it
seems that the extra information isn't that useful for bug reports
because most users install from binaries (for which we already know
the build information).


I thought it was a good idea too when I suggested it. Personnally I do 
not know what are the options used by uwe or Stephan when they compile.


And for linux distributions, many user are not comfortable with using 
--version IMO.


My problem is that we have an extra tab with no additional information. 
Well, with CMake that is.


What useful information is there on Linux with autotools ? (except for 
Qt libs, because those are already in the normal version tab, if one 
removes the #ifdef DEVEL_VERSION).


Vincent

Re: Subject: [PATCH] Make text selectable in Help > About LyX > Version

[Liviu Andronic]

On Thu, Oct 11, 2012 at 11:20 PM, Vincent van Ravesteijn  wrote:
> My problem is that we have an extra tab with no additional information.
> Well, with CMake that is.
>
> What useful information is there on Linux with autotools ? (except for Qt
> libs, because those are already in the normal version tab, if one removes
> the #ifdef DEVEL_VERSION).
>
LyX 2.1.0dev (2011-04-29)
Built on Oct 11 2012, 17:58:16
Configuration
  Host type:x86_64-pc-linux-gnu
  Special build flags:  build=release warnings use-aspell
use-enchant use-hunspell
  C   Compiler: gcc
  C   Compiler LyX flags:
  C   Compiler flags:   -D_FORTIFY_SOURCE=2 -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
  C++ Compiler: g++ (4.6)
  C++ Compiler LyX flags:
  C++ Compiler flags:   -D_FORTIFY_SOURCE=2 -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
  Linker flags:
  Linker user flags:-Wl,-Bsymbolic-functions -Wl,-z,relro
-Wl,-z,defs -Wl,--as-needed -Wl,-z,defs -Wl,--as-needed
  Qt 4 Frontend:
  Qt 4 version: 4.8.1
  Packaging:posix
  LyX binary dir:   /usr/bin
  LyX files dir:/usr/share/lyx2.1


Personally I find the build date very useful and, as JMarc suggested,
it would be nice to have the GIT revision there, too. All in all this
new tab is useful for reporting bugs.

Liviu