Re: Error in build process on Windows 7, using Visual Studio 2012

[Stephan Witt]

Am 15.10.2012 um 23:49 schrieb Kornel Benko kor...@lyx.org:

 Am Montag, 15. Oktober 2012 um 23:09:27, schrieb Stephan Witt 
 st.w...@gmx.net
   I would like to know:

   Is the problem in
 * Compiling: maybe a missing include reference (something not 
   defined?)
 * Linking: maybe missing needed library (which externals are not 
   resolved?)

   [snip]

 Kornel
  
  This is the problem I have on Mac OS X with cmake:
  
  make: *** No rule to make target 
  `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert', needed by 
  `/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'.
Stop.
  
  The build remains unfinished and the LyX binary cannot be started until I 
  change the build target from default ALL_BUILD to LyX.
  
  Stephan
  
 Maybe an error in naming executables on MAC?
  
 The commands to create are used in macro sources.
  
 Expanding it for sources(check_convert a1 a2 a3)
  
   set(check_convert_SOURCES a1 a2 a3)
   add_executable(check_convert ${TOP_SRC_DIR}/src/support/tests/a1 ...)
   target_link_libraries(check_convert support ${Lyx_Boost_Libraries} 
 ${QT_QTCORE_LIBRARY} ${ZLIB_LIBRARY} ${LIBINTL_LIBRARIES} ${ICONV_LIBRARY})
  
 So, is there anywhere a target check_convert?

Yes. I think the problem is not the production of check_convert. The problem is 
the dependency in src/support/tests/regfiles.

The binary `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' is 
never build by Xcode. In case one builds for Debug check_convert is produced in 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release build.

IMHO, either CMAKE_BINARY_DIR has the wrong value or it's the wrong macro in 
lyx/src/support/tests/CMakeLists.txt in the _depends computation.

Stephan

Re: Error in build process on Windows 7, using Visual Studio 2012

[Stephan Witt]

Am 16.10.2012 um 08:17 schrieb Stephan Witt st.w...@gmx.net:

 Am 15.10.2012 um 23:49 schrieb Kornel Benko kor...@lyx.org:
 
 Am Montag, 15. Oktober 2012 um 23:09:27, schrieb Stephan Witt 
 st.w...@gmx.net
 I would like to know:
 
 Is the problem in
  * Compiling: maybe a missing include reference (something not 
 defined?)
  * Linking: maybe missing needed library (which externals are not 
 resolved?)
 
 [snip]
 
  Kornel
 
 This is the problem I have on Mac OS X with cmake:
 
 make: *** No rule to make target 
 `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert', needed by 
 `/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'.
   Stop.
 
 The build remains unfinished and the LyX binary cannot be started until I 
 change the build target from default ALL_BUILD to LyX.
 
 Stephan
 
 Maybe an error in naming executables on MAC?
 
 The commands to create are used in macro sources.
 
 Expanding it for sources(check_convert a1 a2 a3)
 
  set(check_convert_SOURCES a1 a2 a3)
  add_executable(check_convert ${TOP_SRC_DIR}/src/support/tests/a1 ...)
  target_link_libraries(check_convert support ${Lyx_Boost_Libraries} 
 ${QT_QTCORE_LIBRARY} ${ZLIB_LIBRARY} ${LIBINTL_LIBRARIES} ${ICONV_LIBRARY})
 
 So, is there anywhere a target check_convert?
 
 Yes. I think the problem is not the production of check_convert. The problem 
 is the dependency in src/support/tests/regfiles.
 
 The binary `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' is 
 never build by Xcode. In case one builds for Debug check_convert is produced 
 in `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
 `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release build.

Sorry, this was not correct (I made the paths manually):
the binary paths are `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug' 
resp. `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Release'.

Stephan

Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 08:40:12, schrieb Stephan Witt 
st.w...@gmx.net
  Yes. I think the problem is not the production of check_convert. The 
  problem is the dependency in src/support/tests/regfiles.
  
  The binary `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' 
  is never build by Xcode. In case one builds for Debug check_convert is 
  produced in `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
  `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release build.
 
 Sorry, this was not correct (I made the paths manually):
 the binary paths are `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug' 
 resp. `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Release'.
 
 Stephan

OK, I have a new version. This time omitting the path to executables.
Could you please try and report?

Since add_executable(xx ...) creates a target xx, we can depend on that.
And calling xx without path works here. To quote cmake man:

   If COMMAND specifies an executable target (created by ADD_EXECUTABLE)
   it will automatically be replaced by the location of the executable
   created at build time.  Additionally a target-level dependency will be
   added so that the executable target will be built before any target
   using this custom command.  However this does NOT add a file-level
   dependency that would cause the custom command to re-run whenever the
   executable is recompiled.


It should work now.

Kornel
diff --git a/src/support/tests/CMakeLists.txt b/src/support/tests/CMakeLists.txt
index 213b578..c2fb8c6 100644
--- a/src/support/tests/CMakeLists.txt
+++ b/src/support/tests/CMakeLists.txt
@@ -36,10 +36,10 @@ foreach(_src ${check_PROGRAMS})
 	add_custom_command(
 		OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}
 		COMMAND ${CMAKE_COMMAND} -E make_directory ${CMAKE_CURRENT_BINARY_DIR}/regfiles
-		COMMAND ${CMAKE_BINARY_DIR}/bin/${_src}  ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}
+		COMMAND ${_src}  ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}
 		COMMAND ${CMAKE_COMMAND} -E compare_files ${TOP_SRC_DIR}/src/support/tests/regfiles/${_srcx} ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}
-		DEPENDS	${CMAKE_BINARY_DIR}/bin/${_src} ${TOP_SRC_DIR}/src/support/tests/regfiles/${_srcx}
-		COMMENT '${CMAKE_BINARY_DIR}/bin/${_src}'  '${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}'
+		DEPENDS	${_src} ${TOP_SRC_DIR}/src/support/tests/regfiles/${_srcx}
+		COMMENT ${_src}  '${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}'
 	)
 	list(APPEND _depends ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src})
 endforeach()


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

Re: Error in build process on Windows 7, using Visual Studio 2012

[Stephan Witt]

Am 16.10.2012 um 09:17 schrieb Kornel Benko kor...@lyx.org:

 Am Dienstag, 16. Oktober 2012 um 08:40:12, schrieb Stephan Witt 
 st.w...@gmx.net
   Yes. I think the problem is not the production of check_convert. The 
   problem is the dependency in src/support/tests/regfiles.
   
   The binary 
   `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' is never 
   build by Xcode. In case one builds for Debug check_convert is produced in 
   `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
   `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release 
   build.
  
  Sorry, this was not correct (I made the paths manually):
  the binary paths are 
  `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug' resp. 
  `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Release'.
  
  Stephan
  
 OK, I have a new version. This time omitting the path to executables.
 Could you please try and report?
  
 Since add_executable(xx ...) creates a target xx, we can depend on that.
 And calling xx without path works here. To quote cmake man:
  
If COMMAND specifies an executable target (created by ADD_EXECUTABLE)
it will automatically be replaced by the location of the executable
created at build time.  Additionally a target-level dependency will be
added so that the executable target will be built before any target
using this custom command.  However this does NOT add a file-level
dependency that would cause the custom command to re-run whenever the
executable is recompiled.
  
  
 It should work now.
  

It's somewhat better now, but not working.

make: *** No rule to make target 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert', needed 
by 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'.
  Stop.
Command /bin/sh failed with exit code 2

The used Makefile is as follows:
 
src/support/tests/CMakeScripts/check_convert_cmakeRulesBuildPhase.makeDebug 
=
# Generated by CMake, DO NOT EDIT
# Custom rules for check_convert
.SUFFIXES: 
all: \
   
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert


/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert:
 \
/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert\
/Users/stephan/git/lyx/src/support/tests/regfiles/convert
   echo check_convert  
'/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'
   /opt/local/bin/cmake -E make_directory 
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles
   /Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert  
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert
   /opt/local/bin/cmake -E compare_files 
/Users/stephan/git/lyx/src/support/tests/regfiles/convert 
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert
 
src/support/tests/CMakeScripts/check_convert_cmakeRulesBuildPhase.makeDebug 
=

Maybe the target regfiles is executed before the check_convert binary is made?

Stephan

Re: About LyX menus usability.

[Guenter Milde]

On 2012-10-11, Kornel Benko wrote:

 [-- Type: text/plain, Encoding: 7bit --]

 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

-1 Please don't hide this, I need it in every letter I write with LyX
   (because the date should not update with every recompilation).

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

 -1
 Used also as entry in table of content

-4 It is used for optional arguments in many places 
   (e.g. configuring lists with the enumitem module).
   
   However, I strongly suggest to rename it to something less missleading than
   short title.

Günter

Re: About LyX menus usability.

[Jürgen Spitzmüller]

Guenter Milde wrote:
However, I strongly suggest to rename it to something less missleading
 than short title.

The often-discussed solution is outlined here:
http://www.lyx.org/trac/ticket/6753#comment:2

I'll try to get this done for 2.1.

Jürgen

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
 On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda sa...@lyx.org wrote:
  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
 
 Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

It is usually done just before release. Few related things:
- in trunk use change tracking (again, merged before release)
- for manuals maintained by Uwe 
(http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
  ask for his policies ;)

Pavel

Re: Re: [LyX master] * sk.po

[Pavel Sanda]

Kornel Benko wrote:
 Don't worry, maybe I shouldn't commit so often :)

What about using your own branch and merge it monthly or so?
Often .po changes are somewhat painful when doing full searches
in commit history because you get many false positives...

Pavel

Re: Re: Re: [LyX master] * sk.po

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 12:26:36, schrieb Pavel Sanda sa...@lyx.org
 Kornel Benko wrote:
  Don't worry, maybe I shouldn't commit so often :)
 
 What about using your own branch and merge it monthly or so?
 Often .po changes are somewhat painful when doing full searches
 in commit history because you get many false positives...
 
 Pavel

I try to commit as little as possible. Only _really_ changed entries.

Kornel

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

Re: Re: Re: [LyX master] * sk.po

[Pavel Sanda]

Kornel Benko wrote:
 Am Dienstag, 16. Oktober 2012 um 12:26:36, schrieb Pavel Sanda sa...@lyx.org
  Kornel Benko wrote:
   Don't worry, maybe I shouldn't commit so often :)
  
  What about using your own branch and merge it monthly or so?
  Often .po changes are somewhat painful when doing full searches
  in commit history because you get many false positives...
  
  Pavel
 
 I try to commit as little as possible. Only _really_ changed entries.

If you used your own branch you can commit 10xtimes a day without worries ;)
P

Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Vincent van Ravesteijn]

 Yes, but nonetheless I'd like to have it resolved.

 I would like to know:



 Is the problem in

 * Compiling: maybe a missing include reference (something not defined?)

 * Linking: maybe missing needed library (which externals are not resolved?)




 Kornel



Last time I checked I had the following problems:

- there is a missing #include string,
- iconv.lib and intl.lib are not used by the linker,
- the executable could not be found (it is in a Debug directory),
- to be able to run the executable, it should be installed along with the
necessary dlls,

I will check the current status later.

Vincent

About USE_META_KEYBINDING (Stephan?)

[Jean-Marc Lasgouttes]

While investigating ticket #8364, I stumbled on commit e9d943ae, which 
does changes to KeySequence.cpp like:


case 'm': case 'M':
+#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING)
+   mod |= MetaModifier;
+   i += 2;
+   continue;
+#endif

It happens that this USE_META_KEYBINDING macro is not defined anywhere. 
What is the intent here? Only handle Alt and Meta separately? Is this 
documented somewhere?


Why not just define USE_META_KEYBINDING in configure for the mac build?

JMarc

Re: About LyX menus usability.

[Tommaso Cucinotta]

On 15/10/12 21:41, Andrew Parsloe wrote:
The New Oxf. Dict. gives the familiar computer usage against pane 
and no such use against panel (but my copy of the dictionary dates 
from the 1990s). This suggests (but not strongly) that pane should 
be used.


Pushed a couple of commits, let's see how it goes.

T.

Re: About LyX menus usability.

[Tommaso Cucinotta]

On 13/10/12 10:42, Jean-Marc Lasgouttes wrote:

Messages should be renamed message pane (panel?)


so it is now (pane)


LaTeX source = LaTeX Source Pane


it doesn't show merely latex (even though it might be considered the 
main functionality), but also various other formats, which, ehm, 
from the LyX viewpoint, are not really source, but rather export 
formats :-) ?
Cannot think of a better name, for now that entry is Source Pane 
(similarly to other panes).


T.

Re: About LyX menus usability.

[Tommaso Cucinotta]

On 11/10/12 17:48, Jürgen Spitzmüller wrote:

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).


So, the footnote seems critical and everyone wants it very handy. Not 
touching it. Btw, it's quickly available through the toolbar.


However, nobody seems to care about marginal note. So, I would readily 
move it to the Insert-Note sub-menu. At least, it will be 1 less entry 
in the crowded Insert menu.


I also noticed that the [Insert]-[LyX Note] function is called merely 
Insert Note in the toolbar tooltip. Should that be changed to Insert 
LyX Note as well ?
(assuming the user grasps the difference between a LyX note and a 
comment note -- what is it supposed to be ? Both don't seem to show up 
in the PDF, but only the comment goes into the latex).


T.

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Tue, Oct 16, 2012 at 6:25 AM, Pavel Sanda sa...@lyx.org wrote:
 Scott Kostyshak wrote:
 On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda sa...@lyx.org wrote:
  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

 Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

 It is usually done just before release. Few related things:
 - in trunk use change tracking (again, merged before release)
 - for manuals maintained by Uwe 
 (http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
   ask for his policies ;)

OK thanks for the tips. I'm guessing it's OK to update the format in
trunk when changing the manuals?

I don't think anything in-depth needs to be written there about knitr
in the Additional manual because knitr already has a manual for use
with LyX. However, it is currently an example. The only thing
unmanual-like about knitr.lyx is its length, but in my opinion it is
sufficient as is, especially because a lot that is in the Sweave
manual applies to knitr.

Attached is a patch to update the Additional manual. Is it OK?

Thanks,

Scott


0001-Additional.lyx-references-to-knitr-Sweave-doc.patch
Description: Binary data

Re: Press about LyX

[Jerry]

Hi Daniel,

Thanks for this nice article. May I make a suggestion? I think you should show 
at least one example of rendered LyX output so that the reader understands 
better that what you see is not what is shown on the LyX screen, but much 
better and better than typical Word output.

Jerry
(not a developer)

On Oct 16, 2012, at 6:10 AM, HowToAnswer wrote:

 Hi,
 
 I recently finished my article about LyX, here it is :
 
 http://www.howtoanswer.com/a-quick-review-of-lyx--9.html
 
 According to this page, I should notify someone from LyX.
 
 http://www.lyx.org/PressAboutLyX
 
 How can I get in touch with someone from LyX community
 and (if possible) get listed there?
 
 Regards,
 Daniel

$$e not set on import -- import of .Rnw (knitr) fails

[Scott Kostyshak]

I have this problem on master and 2.0.x.

An empty $$e variable is being passed to the converter script on
import because the document is not open yet:
command = subst(command, token_encoding, buffer ?
buffer-params().encoding().iconvName() : string());

Should $$e be set to the default encoding of a new document?

Or is this something that the converter script should deal with?

To reproduce:
1. Open examples/knitr.lyx
2. Export to Rnw (knitr)
3. Import the Rnw (knitr) file

I get an error after (3) because lyxknitr.R is expecting a non-empty
$$e argument.

Re: About USE_META_KEYBINDING (Stephan?)

[Stephan Witt]

Am 16.10.2012 um 23:39 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org:

 While investigating ticket #8364, I stumbled on commit e9d943ae, which does 
 changes to KeySequence.cpp like:
 
case 'm': case 'M':
 +#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING)
 +   mod |= MetaModifier;
 +   i += 2;
 +   continue;
 +#endif
 
 It happens that this USE_META_KEYBINDING macro is not defined anywhere. What 
 is the intent here? Only handle Alt and Meta separately? Is this documented 
 somewhere?

I used USE_MACOSX_PACKAGING because of the low afford and it is a must for Mac 
OS X.
I didn't understand why it is not needed on other platforms, therefor I 
introduced USE_META_KEYBINDING to play with it.
But I didn't finish it…

 Why not just define USE_META_KEYBINDING in configure for the mac build?


Yes, this can be done.

Other options are
1) to remove the USE_META_KEYBINDING macro
2) to handle Alt and Meta separately on all platforms

Stephan

Re: Error in build process on Windows 7, using Visual Studio 2012

[Stephan Witt]

Am 15.10.2012 um 23:49 schrieb Kornel Benko :

> Am Montag, 15. Oktober 2012 um 23:09:27, schrieb Stephan Witt 
> 
> > > I would like to know:
> > >  
> > > Is the problem in
> > >   * Compiling: maybe a missing include reference (something not 
> > > defined?)
> > >   * Linking: maybe missing needed library (which externals are not 
> > > resolved?)
> > >  
> > > [snip]
> > >  
> > >   Kornel
> > 
> > This is the problem I have on Mac OS X with cmake:
> > 
> > make: *** No rule to make target 
> > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert', needed by 
> > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'.
> >   Stop.
> > 
> > The build remains unfinished and the LyX binary cannot be started until I 
> > change the build target from default ALL_BUILD to LyX.
> > 
> > Stephan
>  
> Maybe an error in naming executables on MAC?
>  
> The commands to create are used in macro sources.
>  
> Expanding it for sources(check_convert a1 a2 a3)
>  
>   set(check_convert_SOURCES a1 a2 a3)
>   add_executable(check_convert "${TOP_SRC_DIR}/src/support/tests/a1" ...)
>   target_link_libraries(check_convert support ${Lyx_Boost_Libraries} 
> ${QT_QTCORE_LIBRARY} ${ZLIB_LIBRARY} ${LIBINTL_LIBRARIES} ${ICONV_LIBRARY})
>  
> So, is there anywhere a target check_convert?

Yes. I think the problem is not the production of check_convert. The problem is 
the dependency in src/support/tests/regfiles.

The binary `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' is 
never build by Xcode. In case one builds for Debug check_convert is produced in 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release build.

IMHO, either CMAKE_BINARY_DIR has the wrong value or it's the wrong macro in 
lyx/src/support/tests/CMakeLists.txt in the _depends computation.

Stephan

Re: Error in build process on Windows 7, using Visual Studio 2012

[Stephan Witt]

Am 16.10.2012 um 08:17 schrieb Stephan Witt :

> Am 15.10.2012 um 23:49 schrieb Kornel Benko :
> 
>> Am Montag, 15. Oktober 2012 um 23:09:27, schrieb Stephan Witt 
>> 
 I would like to know:
 
 Is the problem in
  * Compiling: maybe a missing include reference (something not 
 defined?)
  * Linking: maybe missing needed library (which externals are not 
 resolved?)
 
 [snip]
 
  Kornel
>>> 
>>> This is the problem I have on Mac OS X with cmake:
>>> 
>>> make: *** No rule to make target 
>>> `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert', needed by 
>>> `/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'.
>>>   Stop.
>>> 
>>> The build remains unfinished and the LyX binary cannot be started until I 
>>> change the build target from default ALL_BUILD to LyX.
>>> 
>>> Stephan
>> 
>> Maybe an error in naming executables on MAC?
>> 
>> The commands to create are used in macro sources.
>> 
>> Expanding it for sources(check_convert a1 a2 a3)
>> 
>>  set(check_convert_SOURCES a1 a2 a3)
>>  add_executable(check_convert "${TOP_SRC_DIR}/src/support/tests/a1" ...)
>>  target_link_libraries(check_convert support ${Lyx_Boost_Libraries} 
>> ${QT_QTCORE_LIBRARY} ${ZLIB_LIBRARY} ${LIBINTL_LIBRARIES} ${ICONV_LIBRARY})
>> 
>> So, is there anywhere a target check_convert?
> 
> Yes. I think the problem is not the production of check_convert. The problem 
> is the dependency in src/support/tests/regfiles.
> 
> The binary `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' is 
> never build by Xcode. In case one builds for Debug check_convert is produced 
> in `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
> `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release build.

Sorry, this was not correct (I made the paths manually):
the binary paths are `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug' 
resp. `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Release'.

Stephan

Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 08:40:12, schrieb Stephan Witt 

> > Yes. I think the problem is not the production of check_convert. The 
> > problem is the dependency in src/support/tests/regfiles.
> > 
> > The binary `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' 
> > is never build by Xcode. In case one builds for Debug check_convert is 
> > produced in `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
> > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release build.
> 
> Sorry, this was not correct (I made the paths manually):
> the binary paths are `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug' 
> resp. `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Release'.
> 
> Stephan

OK, I have a new version. This time omitting the path to executables.
Could you please try and report?

Since add_executable(xx ...) creates a target "xx", we can depend on that.
And calling "xx" without path works here. To quote cmake man:

   If COMMAND specifies an executable target (created by ADD_EXECUTABLE)
   it will automatically be replaced by the location of the executable
   created at build time.  Additionally a target-level dependency will be
   added so that the executable target will be built before any target
   using this custom command.  However this does NOT add a file-level
   dependency that would cause the custom command to re-run whenever the
   executable is recompiled.


It should work now.

Kornel
diff --git a/src/support/tests/CMakeLists.txt b/src/support/tests/CMakeLists.txt
index 213b578..c2fb8c6 100644
--- a/src/support/tests/CMakeLists.txt
+++ b/src/support/tests/CMakeLists.txt
@@ -36,10 +36,10 @@ foreach(_src ${check_PROGRAMS})
 	add_custom_command(
 		OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}
 		COMMAND ${CMAKE_COMMAND} -E make_directory "${CMAKE_CURRENT_BINARY_DIR}/regfiles"
-		COMMAND "${CMAKE_BINARY_DIR}/bin/${_src}" > ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}
+		COMMAND ${_src} > ${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}
 		COMMAND ${CMAKE_COMMAND} -E compare_files "${TOP_SRC_DIR}/src/support/tests/regfiles/${_srcx}" "${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}"
-		DEPENDS	"${CMAKE_BINARY_DIR}/bin/${_src}" "${TOP_SRC_DIR}/src/support/tests/regfiles/${_srcx}"
-		COMMENT "'${CMAKE_BINARY_DIR}/bin/${_src}' > '${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}'"
+		DEPENDS	${_src} "${TOP_SRC_DIR}/src/support/tests/regfiles/${_srcx}"
+		COMMENT "${_src} > '${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}'"
 	)
 	list(APPEND _depends "${CMAKE_CURRENT_BINARY_DIR}/regfiles/${_src}")
 endforeach()


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

Re: Error in build process on Windows 7, using Visual Studio 2012

[Stephan Witt]

Am 16.10.2012 um 09:17 schrieb Kornel Benko :

> Am Dienstag, 16. Oktober 2012 um 08:40:12, schrieb Stephan Witt 
> 
> > > Yes. I think the problem is not the production of check_convert. The 
> > > problem is the dependency in src/support/tests/regfiles.
> > > 
> > > The binary 
> > > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/check_convert' is never 
> > > build by Xcode. In case one builds for Debug check_convert is produced in 
> > > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Debug/bin' and in 
> > > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/Release/bin' for Release 
> > > build.
> > 
> > Sorry, this was not correct (I made the paths manually):
> > the binary paths are 
> > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug' resp. 
> > `/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Release'.
> > 
> > Stephan
>  
> OK, I have a new version. This time omitting the path to executables.
> Could you please try and report?
>  
> Since add_executable(xx ...) creates a target "xx", we can depend on that.
> And calling "xx" without path works here. To quote cmake man:
>  
>If COMMAND specifies an executable target (created by ADD_EXECUTABLE)
>it will automatically be replaced by the location of the executable
>created at build time.  Additionally a target-level dependency will be
>added so that the executable target will be built before any target
>using this custom command.  However this does NOT add a file-level
>dependency that would cause the custom command to re-run whenever the
>executable is recompiled.
>  
>  
> It should work now.
>  

It's somewhat better now, but not working.

make: *** No rule to make target 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert', needed 
by 
`/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'.
  Stop.
Command /bin/sh failed with exit code 2

The used Makefile is as follows:
 
src/support/tests/CMakeScripts/check_convert_cmakeRulesBuildPhase.makeDebug 
=
# Generated by CMake, DO NOT EDIT
# Custom rules for check_convert
.SUFFIXES: 
all: \
   
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert


/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert:
 \
/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert\
/Users/stephan/git/lyx/src/support/tests/regfiles/convert
   echo "check_convert > 
'/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert'"
   /opt/local/bin/cmake -E make_directory 
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles
   /Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert > 
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert
   /opt/local/bin/cmake -E compare_files 
/Users/stephan/git/lyx/src/support/tests/regfiles/convert 
/Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/regfiles/check_convert
 
src/support/tests/CMakeScripts/check_convert_cmakeRulesBuildPhase.makeDebug 
=

Maybe the target regfiles is executed before the check_convert binary is made?

Stephan

Re: About LyX menus & usability.

[Guenter Milde]

On 2012-10-11, Kornel Benko wrote:

> [-- Type: text/plain, Encoding: 7bit --]

> 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

-1 Please don't hide this, I need it in every letter I write with LyX
   (because the date should not update with every recompilation).

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

> -1
> Used also as entry in table of content

-4 It is used for optional arguments in many places 
   (e.g. configuring lists with the enumitem module).
   
   However, I strongly suggest to rename it to something less missleading than
   "short title".

Günter

Re: About LyX menus & usability.

[Jürgen Spitzmüller]

Guenter Milde wrote:
>However, I strongly suggest to rename it to something less missleading
> than "short title".

The often-discussed solution is outlined here:
http://www.lyx.org/trac/ticket/6753#comment:2

I'll try to get this done for 2.1.

Jürgen

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
> On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda  wrote:
> > 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
> 
> Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

It is usually done just before release. Few related things:
- in trunk use change tracking (again, merged before release)
- for manuals maintained by Uwe 
(http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
  ask for his policies ;)

Pavel

Re: Re: [LyX master] * sk.po

[Pavel Sanda]

Kornel Benko wrote:
> Don't worry, maybe I shouldn't commit so often :)

What about using your own branch and merge it monthly or so?
Often .po changes are somewhat painful when doing full searches
in commit history because you get many false positives...

Pavel

Re: Re: Re: [LyX master] * sk.po

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 12:26:36, schrieb Pavel Sanda 
> Kornel Benko wrote:
> > Don't worry, maybe I shouldn't commit so often :)
> 
> What about using your own branch and merge it monthly or so?
> Often .po changes are somewhat painful when doing full searches
> in commit history because you get many false positives...
> 
> Pavel

I try to commit as little as possible. Only _really_ changed entries.

Kornel

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

Re: Re: Re: [LyX master] * sk.po

[Pavel Sanda]

Kornel Benko wrote:
> Am Dienstag, 16. Oktober 2012 um 12:26:36, schrieb Pavel Sanda 
> > Kornel Benko wrote:
> > > Don't worry, maybe I shouldn't commit so often :)
> > 
> > What about using your own branch and merge it monthly or so?
> > Often .po changes are somewhat painful when doing full searches
> > in commit history because you get many false positives...
> > 
> > Pavel
> 
> I try to commit as little as possible. Only _really_ changed entries.

If you used your own branch you can commit 10xtimes a day without worries ;)
P

Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Vincent van Ravesteijn]

>
>
>
>
> Yes, but nonetheless I'd like to have it resolved.
>
> I would like to know:
>
>
>
> Is the problem in
>
> * Compiling: maybe a missing include reference (something not defined?)
>
> * Linking: maybe missing needed library (which externals are not resolved?)
>
>
>
>
> Kornel
>


Last time I checked I had the following problems:

- there is a missing #include ,
- iconv.lib and intl.lib are not used by the linker,
- the executable could not be found (it is in a "Debug" directory),
- to be able to run the executable, it should be installed along with the
necessary dlls,

I will check the current status later.

Vincent

About USE_META_KEYBINDING (Stephan?)

[Jean-Marc Lasgouttes]

While investigating ticket #8364, I stumbled on commit e9d943ae, which 
does changes to KeySequence.cpp like:


case 'm': case 'M':
+#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING)
+   mod |= MetaModifier;
+   i += 2;
+   continue;
+#endif

It happens that this USE_META_KEYBINDING macro is not defined anywhere. 
What is the intent here? Only handle Alt and Meta separately? Is this 
documented somewhere?


Why not just define USE_META_KEYBINDING in configure for the mac build?

JMarc

Re: About LyX menus & usability.

[Tommaso Cucinotta]

On 15/10/12 21:41, Andrew Parsloe wrote:
The New Oxf. Dict. gives the familiar computer usage against "pane" 
and no such use against "panel" (but my copy of the dictionary dates 
from the 1990s). This suggests (but not strongly) that "pane" should 
be used.


Pushed a couple of commits, let's see how it goes.

T.

Re: About LyX menus & usability.

[Tommaso Cucinotta]

On 13/10/12 10:42, Jean-Marc Lasgouttes wrote:

Messages should be renamed "message pane" (panel?)


so it is now ("pane")


LaTeX source => "LaTeX Source Pane"


it doesn't show merely latex (even though it might be considered the 
main functionality), but also various other formats, which, ehm, 
from the LyX viewpoint, are not really "source", but rather "export" 
formats :-) ?
Cannot think of a better name, for now that entry is "Source Pane" 
(similarly to other panes).


T.

Re: About LyX menus & usability.

[Tommaso Cucinotta]

On 11/10/12 17:48, Jürgen Spitzmüller wrote:

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).


So, the footnote seems critical and everyone wants it very handy. Not 
touching it. Btw, it's quickly available through the toolbar.


However, nobody seems to care about "marginal note". So, I would readily 
move it to the Insert->Note sub-menu. At least, it will be 1 less entry 
in the "crowded" Insert menu.


I also noticed that the [Insert]->[LyX Note] function is called merely 
"Insert Note" in the toolbar tooltip. Should that be changed to "Insert 
LyX Note" as well ?
(assuming the user grasps the difference between a LyX note and a 
"comment" note -- what is it supposed to be ? Both don't seem to show up 
in the PDF, but only the "comment" goes into the latex).


T.

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Tue, Oct 16, 2012 at 6:25 AM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda  wrote:
>> > 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
>>
>> Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?
>
> It is usually done just before release. Few related things:
> - in trunk use change tracking (again, merged before release)
> - for manuals maintained by Uwe 
> (http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
>   ask for his policies ;)

OK thanks for the tips. I'm guessing it's OK to update the format in
trunk when changing the manuals?

I don't think anything in-depth needs to be written there about knitr
in the Additional manual because knitr already has a "manual" for use
with LyX. However, it is currently an example. The only thing
unmanual-like about knitr.lyx is its length, but in my opinion it is
sufficient as is, especially because a lot that is in the Sweave
manual applies to knitr.

Attached is a patch to update the Additional manual. Is it OK?

Thanks,

Scott


0001-Additional.lyx-references-to-knitr-Sweave-doc.patch
Description: Binary data

Re: Press about LyX

[Jerry]

Hi Daniel,

Thanks for this nice article. May I make a suggestion? I think you should show 
at least one example of rendered LyX output so that the reader understands 
better that what you see is not what is shown on the LyX screen, but much 
better and better than typical Word output.

Jerry
(not a developer)

On Oct 16, 2012, at 6:10 AM, HowToAnswer wrote:

> Hi,
> 
> I recently finished my article about LyX, here it is :
> 
> http://www.howtoanswer.com/a-quick-review-of-lyx--9.html
> 
> According to this page, I should notify someone from LyX.
> 
> http://www.lyx.org/PressAboutLyX
> 
> How can I get in touch with someone from LyX community
> and (if possible) get listed there?
> 
> Regards,
> Daniel

$$e not set on import --> import of .Rnw (knitr) fails

[Scott Kostyshak]

I have this problem on master and 2.0.x.

An empty $$e variable is being passed to the converter script on
import because the document is not open yet:
command = subst(command, token_encoding, buffer ?
buffer->params().encoding().iconvName() : string());

Should $$e be set to the default encoding of a new document?

Or is this something that the converter script should deal with?

To reproduce:
1. Open examples/knitr.lyx
2. Export to Rnw (knitr)
3. Import the Rnw (knitr) file

I get an error after (3) because lyxknitr.R is expecting a non-empty
$$e argument.

Re: About USE_META_KEYBINDING (Stephan?)

[Stephan Witt]

Am 16.10.2012 um 23:39 schrieb Jean-Marc Lasgouttes :

> While investigating ticket #8364, I stumbled on commit e9d943ae, which does 
> changes to KeySequence.cpp like:
> 
>case 'm': case 'M':
> +#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING)
> +   mod |= MetaModifier;
> +   i += 2;
> +   continue;
> +#endif
> 
> It happens that this USE_META_KEYBINDING macro is not defined anywhere. What 
> is the intent here? Only handle Alt and Meta separately? Is this documented 
> somewhere?

I used USE_MACOSX_PACKAGING because of the low afford and it is a must for Mac 
OS X.
I didn't understand why it is not needed on other platforms, therefor I 
introduced USE_META_KEYBINDING to play with it.
But I didn't finish it…

> Why not just define USE_META_KEYBINDING in configure for the mac build?


Yes, this can be done.

Other options are
1) to remove the USE_META_KEYBINDING macro
2) to handle Alt and Meta separately on all platforms

Stephan