RE: insert bibtex bibliography GUI proposal
From: Jürgen Spitzmüller [sp...@lyx.org] Sent: Friday, June 01, 2012 5:07 AM John Tapsell wrote: If you need people to read documentation, the GUI is too complicated. It should be so simple that you don't need documentation. Good point. I'm not completely convinced by this argument (although it does sound like a good general rule). Without GUI documentation, a lot of the LyX manuals would be more like LaTeX manuals. It seems like there are two workflows of users: (1) put your .bib files in your texmf path (2) put your .bib files with your project files Jürgen, I get the feeling that you do recognize that (2) is legitimate for some cases, but that the most common case should be (1) and that people often do (2) when they should be doing (1). So the main question this comes down to is: even though the newbie which we are trying to program for does (2) more often than (1), should we make (1) easier to do than (2) in order to encourage the user to do what is considered right? Or should we make the default the thing that is most natural to him? I see a few options here: (a) keep things how they are (and add some tooltips, as Jürgen suggested). (b) do what I originally proposed which is have two Add buttons. This would make (1) as easy as (2). (c) have a User .bib folder path in the Paths of LyX Preferences. This would encourage the good practice of having a common database but the user would not have to know anything about TEX paths. (d1) Have an option to hide databases from the global texmf path and only show the databases in $TEXMFHOME (suggested by Jürgen). (d2) I would tweak (d1) slightly to have the default as showing the databases from $TEXMFHOME and the option be to show the databases from the global texmf path. Any opinions? Thanks, Scott
RE: no GUI error when configure fails on first configure
From: Richard Heck [rgh...@comcast.net] Sent: Monday, May 21, 2012 10:20 AM OK, I see the problem. Richard, are you able to add this to your todo list? Should I open a trac ticket? Thanks, Scott
RE: why does import save?
From: John McCabe-Dansted [gma...@gmail.com] Sent: Wednesday, May 23, 2012 11:02 PM On Wed, May 23, 2012 at 8:52 PM, Richard Heck rgh...@comcast.net wrote: I agree with you generally here. The conversion, like for export, should be done in a temporary directory, if only because the importer could, in principle, create all kinds of garbage in the original directory. Then the One thing is that the present importer also appears to import child .tex files. If we lose the convert and open semantics, we must consider: do we want to try to preserve links to the imported child files? If so, how? Any other opinions on this? Should I move the conversation to a trac ticket? Scott
Re: Unable to Push New Tag
On 26 June 2012 20:32, Richard Heck rgh...@lyx.org wrote: On 06/26/2012 12:20 PM, Vincent van Ravesteijn wrote: Op 26-6-2012 17:48, Richard Heck schreef: Anyone know how to fix this? Or am I doing something wrong? Richard You need to have permissions to create a new branch. Find the gitolite.conf file in the gitolite-admin.git repo and give yourself rights (RW - RWC). I found one at ~git/.gitolite/conf/gitolite.conf, but changing it seems to have no effect. Looks as if one is supposed to clone and then push that repo, which only Lars seems to have the right to do. If you did changes there you might have broken everything. -- Lgb
Re: [LyX master] Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION
Le 04/07/2012 12:19, Jean-Marc Lasgouttes a écrit : The branch, master, has been updated. - Log - commit 4471e65fa19135652874a9fde948c7d6dd54c261 Author: Jean-Marc Lasgouttes lasgout...@lyx.org Date: Wed Jul 4 12:18:15 2012 +0200 Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION Richard, to branch? Without this the current branch version is not understood as development (only svn is tested). JMarc diff --git a/config/lyxinclude.m4 b/config/lyxinclude.m4 index ed12f3d..d915d5c 100644 --- a/config/lyxinclude.m4 +++ b/config/lyxinclude.m4 @@ -22,7 +22,7 @@ AC_ARG_ENABLE(build-type, *) AC_ERROR([Bad build type specification \$enableval\. Please use one of rel(ease), pre(release), dev(elopment), prof(iling), or gprof]);; esac], [case AC_PACKAGE_VERSION in -*svn*) build_type=development;; +*svn*|*dev*) build_type=development;; *pre*|*alpha*|*beta*|*rc*) build_type=prerelease;; *) build_type=release ;; esac]) --- Summary of changes: config/lyxinclude.m4 |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive
Re: [LyX master] Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION
On 07/04/2012 06:21 AM, Jean-Marc Lasgouttes wrote: Le 04/07/2012 12:19, Jean-Marc Lasgouttes a écrit : The branch, master, has been updated. - Log - commit 4471e65fa19135652874a9fde948c7d6dd54c261 Author: Jean-Marc Lasgouttes lasgout...@lyx.org Date: Wed Jul 4 12:18:15 2012 +0200 Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION Richard, to branch? Without this the current branch version is not understood as development (only svn is tested). Yes, thanks. Richard JMarc diff --git a/config/lyxinclude.m4 b/config/lyxinclude.m4 index ed12f3d..d915d5c 100644 --- a/config/lyxinclude.m4 +++ b/config/lyxinclude.m4 @@ -22,7 +22,7 @@ AC_ARG_ENABLE(build-type, *) AC_ERROR([Bad build type specification \$enableval\. Please use one of rel(ease), pre(release), dev(elopment), prof(iling), or gprof]);; esac], [case AC_PACKAGE_VERSION in -*svn*) build_type=development;; +*svn*|*dev*) build_type=development;; *pre*|*alpha*|*beta*|*rc*) build_type=prerelease;; *) build_type=release ;; esac]) --- Summary of changes: config/lyxinclude.m4 |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive
Re: [LyX master] Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION
Le 04/07/2012 16:37, Richard Heck a écrit : commit 4471e65fa19135652874a9fde948c7d6dd54c261 Author: Jean-Marc Lasgouttes lasgout...@lyx.org Date: Wed Jul 4 12:18:15 2012 +0200 Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION Richard, to branch? Without this the current branch version is not understood as development (only svn is tested). Yes, thanks. Done. JMarc
Re: Windows installer for LyX 2.0.4
Am 04.07.2012 00:28, schrieb Richard Heck: You Windows people should decide what makes sense. As I have shown in my screenshot the other programs use also the scheme Name major.sub, so LyX 2.0 would be the same. I'm allergic to spaces in pathnames myself. They are not a problem. I was using this for years in the old installer and also the other progrmas use spaces, see my screenshot. So this topic is now solved. regards Uwe
Re: [LyX 2.0.x] polyglossia tex2lyx support also for branch
Am 02.07.2012 22:57, schrieb Kornel Benko: The compilation with merged files seemed to be faster on windows. Since then he (Peter) is developing a new generator for cmake called ninja. This one will be (on windows again) really fast compared to I'm already using Ninja and this is indeed much faster, no matter if merged build or not. But I still have not understood why it compiled as merged build and why we use merged builds for releases. thanks and regards Uwe
[patch] fix bug 8230 - was: Re: [LyX 2.0.x] polyglossia tex2lyx support also for branch
Am 03.07.2012 21:01, schrieb Uwe Stöhr: Ah, I tried to output as char and that failed. I'll try now with string and propose a patch. Attached is the patch for bug http://www.lyx.org/trac/ticket/8230 I tested it with all sorts of verbatim that I could imagine and also with single '\' as \verb argument. OK? thanks and regards Uwe diff --git a/C:\\DOCUME~1\\usti\\LOCALS~1\\Temp\\tex14.tmp\\text-HEAD-left.cpp b/D:\\LyXGit\\Master\\src\\tex2lyx\\text.cpp index cebc6fb..091ebd3 100644 --- a/C:\\DOCUME~1\\usti\\LOCALS~1\\Temp\\tex14.tmp\\text-HEAD-left.cpp +++ b/D:\\LyXGit\\Master\\src\\tex2lyx\\text.cpp @@ -3645,12 +3645,18 @@ void parse_text(Parser p, ostream os, unsigned flags, bool outer, } } - else if (t.cs() == verb) { + else if (prefixIs(t.cs(), verb)) { + // as soon as a command begins with \verb, it is verbatim + // for example \verbätimä context.check_layout(os); - char const delimiter = p.next_token().character(); + char delimiter; + docstring s = from_utf8(p.next_token().asInput()); + // cut off the first character (in case there are more) + s = s[0]; + delimiter = to_utf8(s)[0]; string const arg = p.getArg(delimiter, delimiter); ostringstream oss; - oss \\verb delimiter arg delimiter; + oss \\verb to_utf8(s) arg to_utf8(s); handle_ert(os, oss.str(), context); }
Re: r40934 - www-user/trunk/misc/rss
rgh...@lyx.org wrote: Author: rgheck Date: Mon Jul 2 16:00:49 2012 New Revision: 40934 URL: http://www.lyx.org/trac/changeset/40934 Log: Update RSS feed. Sorry if I sound too pushy, but is there some reason why we delay announcement email when RSS and page shows 2.0.4 version? Pavel
Re: Windows installer for LyX 2.0.4
On Wed, Jul 4, 2012 at 11:31 PM, Uwe Stöhr uwesto...@web.de wrote: Am 04.07.2012 00:28, schrieb Richard Heck: I'm allergic to spaces in pathnames myself. They are not a problem. I was using this for years in the old installer and also the other progrmas use spaces, see my screenshot. So this topic is now solved. What about spaces in path names of files? I was quite surprised that LyX couldn't handle that on Windows, and this could be a psychological hurdle to Windows users. Liviu
RE: "insert bibtex bibliography" GUI proposal
From: Jürgen Spitzmüller [sp...@lyx.org] Sent: Friday, June 01, 2012 5:07 AM >John Tapsell wrote: >> If you need people to read documentation, the GUI is too complicated. >> >> It should be so simple that you don't need documentation. >Good point. I'm not completely convinced by this argument (although it does sound like a good general rule). Without GUI documentation, a lot of the LyX manuals would be more like LaTeX manuals. It seems like there are two workflows of users: (1) put your .bib files in your texmf path (2) put your .bib files with your project files Jürgen, I get the feeling that you do recognize that (2) is legitimate for some cases, but that the most common case should be (1) and that people often do (2) when they should be doing (1). So the main question this comes down to is: even though the newbie which we are trying to program for does (2) more often than (1), should we make (1) easier to do than (2) in order to encourage the user to do what is considered right? Or should we make the default the thing that is most natural to him? I see a few options here: (a) keep things how they are (and add some tooltips, as Jürgen suggested). (b) do what I originally proposed which is have two "Add" buttons. This would make (1) as easy as (2). (c) have a "User .bib folder" path in the Paths of LyX Preferences. This would encourage the good practice of having a common database but the user would not have to know anything about TEX paths. (d1) Have an option to hide databases from the global texmf path and only show the databases in $TEXMFHOME (suggested by Jürgen). (d2) I would tweak (d1) slightly to have the default as showing the databases from $TEXMFHOME and the option be to show the databases from the global texmf path. Any opinions? Thanks, Scott
RE: no GUI error when configure fails on first configure
From: Richard Heck [rgh...@comcast.net] Sent: Monday, May 21, 2012 10:20 AM >OK, I see the problem. Richard, are you able to add this to your todo list? Should I open a trac ticket? Thanks, Scott
RE: why does import save?
From: John McCabe-Dansted [gma...@gmail.com] Sent: Wednesday, May 23, 2012 11:02 PM >On Wed, May 23, 2012 at 8:52 PM, Richard Heckwrote: >> I agree with you generally here. The conversion, like for export, should be >> done in a temporary directory, if only because the importer could, in >> principle, create all kinds of garbage in the original directory. Then the > One thing is that the present importer also appears to import child > .tex files. If we lose the convert and open semantics, we must > consider: do we want to try to preserve links to the imported child > files? If so, how? Any other opinions on this? Should I move the conversation to a trac ticket? Scott
Re: Unable to Push New Tag
On 26 June 2012 20:32, Richard Heckwrote: > On 06/26/2012 12:20 PM, Vincent van Ravesteijn wrote: >> >> Op 26-6-2012 17:48, Richard Heck schreef: >>> >>> >>> Anyone know how to fix this? Or am I doing something wrong? >>> >>> Richard >>> >> >> You need to have permissions to "create a new branch". >> >> Find the gitolite.conf file in the gitolite-admin.git repo and give >> yourself rights (RW -> RWC). >> > I found one at ~git/.gitolite/conf/gitolite.conf, but changing it seems to > have no effect. Looks as if one is supposed to clone and then push that > repo, which only Lars seems to have the right to do. If you did changes there you might have broken everything. -- Lgb
Re: [LyX master] Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION
Le 04/07/2012 12:19, Jean-Marc Lasgouttes a écrit : The branch, master, has been updated. - Log - commit 4471e65fa19135652874a9fde948c7d6dd54c261 Author: Jean-Marc LasgouttesDate: Wed Jul 4 12:18:15 2012 +0200 Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION Richard, to branch? Without this the current branch version is not understood as development (only svn is tested). JMarc diff --git a/config/lyxinclude.m4 b/config/lyxinclude.m4 index ed12f3d..d915d5c 100644 --- a/config/lyxinclude.m4 +++ b/config/lyxinclude.m4 @@ -22,7 +22,7 @@ AC_ARG_ENABLE(build-type, *) AC_ERROR([Bad build type specification \"$enableval\". Please use one of rel(ease), pre(release), dev(elopment), prof(iling), or gprof]);; esac], [case AC_PACKAGE_VERSION in -*svn*) build_type=development;; +*svn*|*dev*) build_type=development;; *pre*|*alpha*|*beta*|*rc*) build_type=prerelease;; *) build_type=release ;; esac]) --- Summary of changes: config/lyxinclude.m4 |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive
Re: [LyX master] Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION
On 07/04/2012 06:21 AM, Jean-Marc Lasgouttes wrote: Le 04/07/2012 12:19, Jean-Marc Lasgouttes a écrit : The branch, master, has been updated. - Log - commit 4471e65fa19135652874a9fde948c7d6dd54c261 Author: Jean-Marc LasgouttesDate: Wed Jul 4 12:18:15 2012 +0200 Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION Richard, to branch? Without this the current branch version is not understood as development (only svn is tested). Yes, thanks. Richard JMarc diff --git a/config/lyxinclude.m4 b/config/lyxinclude.m4 index ed12f3d..d915d5c 100644 --- a/config/lyxinclude.m4 +++ b/config/lyxinclude.m4 @@ -22,7 +22,7 @@ AC_ARG_ENABLE(build-type, *) AC_ERROR([Bad build type specification \"$enableval\". Please use one of rel(ease), pre(release), dev(elopment), prof(iling), or gprof]);; esac], [case AC_PACKAGE_VERSION in -*svn*) build_type=development;; +*svn*|*dev*) build_type=development;; *pre*|*alpha*|*beta*|*rc*) build_type=prerelease;; *) build_type=release ;; esac]) --- Summary of changes: config/lyxinclude.m4 |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive
Re: [LyX master] Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION
Le 04/07/2012 16:37, Richard Heck a écrit : commit 4471e65fa19135652874a9fde948c7d6dd54c261 Author: Jean-Marc LasgouttesDate: Wed Jul 4 12:18:15 2012 +0200 Handle version numbers like 2.0.5dev in LYX_CHECK_VERSION Richard, to branch? Without this the current branch version is not understood as development (only svn is tested). Yes, thanks. Done. JMarc
Re: Windows installer for LyX 2.0.4
Am 04.07.2012 00:28, schrieb Richard Heck: You Windows people should decide what makes sense. As I have shown in my screenshot the other programs use also the scheme "Name major.sub", so "LyX 2.0" would be the same. I'm allergic to spaces in pathnames myself. They are not a problem. I was using this for years in the old installer and also the other progrmas use spaces, see my screenshot. So this topic is now solved. regards Uwe
Re: [LyX 2.0.x] polyglossia tex2lyx support also for branch
Am 02.07.2012 22:57, schrieb Kornel Benko: The compilation with merged files seemed to be faster on windows. Since then he (Peter) is developing a new generator for cmake called "ninja". This one will be (on windows again) really fast compared to I'm already using Ninja and this is indeed much faster, no matter if merged build or not. But I still have not understood why it compiled as merged build and why we use merged builds for releases. thanks and regards Uwe
[patch] fix bug 8230 - was: Re: [LyX 2.0.x] polyglossia tex2lyx support also for branch
Am 03.07.2012 21:01, schrieb Uwe Stöhr: Ah, I tried to output as char and that failed. I'll try now with string and propose a patch. Attached is the patch for bug http://www.lyx.org/trac/ticket/8230 I tested it with all sorts of verbatim that I could imagine and also with single '\' as \verb argument. OK? thanks and regards Uwe diff --git "a/C:\\DOCUME~1\\usti\\LOCALS~1\\Temp\\tex14.tmp\\text-HEAD-left.cpp" "b/D:\\LyXGit\\Master\\src\\tex2lyx\\text.cpp" index cebc6fb..091ebd3 100644 --- "a/C:\\DOCUME~1\\usti\\LOCALS~1\\Temp\\tex14.tmp\\text-HEAD-left.cpp" +++ "b/D:\\LyXGit\\Master\\src\\tex2lyx\\text.cpp" @@ -3645,12 +3645,18 @@ void parse_text(Parser & p, ostream & os, unsigned flags, bool outer, } } - else if (t.cs() == "verb") { + else if (prefixIs(t.cs(), "verb")) { + // as soon as a command begins with \verb, it is verbatim + // for example \verbätimä context.check_layout(os); - char const delimiter = p.next_token().character(); + char delimiter; + docstring s = from_utf8(p.next_token().asInput()); + // cut off the first character (in case there are more) + s = s[0]; + delimiter = to_utf8(s)[0]; string const arg = p.getArg(delimiter, delimiter); ostringstream oss; - oss << "\\verb" << delimiter << arg << delimiter; + oss << "\\verb" << to_utf8(s) << arg << to_utf8(s); handle_ert(os, oss.str(), context); }
Re: r40934 - www-user/trunk/misc/rss
rgh...@lyx.org wrote: > Author: rgheck > Date: Mon Jul 2 16:00:49 2012 > New Revision: 40934 > URL: http://www.lyx.org/trac/changeset/40934 > > Log: > Update RSS feed. Sorry if I sound too pushy, but is there some reason why we delay announcement email when RSS and page shows 2.0.4 version? Pavel
Re: Windows installer for LyX 2.0.4
On Wed, Jul 4, 2012 at 11:31 PM, Uwe Stöhrwrote: > Am 04.07.2012 00:28, schrieb Richard Heck: >> I'm allergic to spaces in pathnames myself. > > They are not a problem. I was using this for years in the old installer and > also the other progrmas use spaces, see my screenshot. > > So this topic is now solved. > What about spaces in path names of files? I was quite surprised that LyX couldn't handle that on Windows, and this could be a psychological hurdle to Windows users. Liviu