Re: Help with paragraph breaks on LyX 2.0.4 (Mac)
Hello Daisuke, > I would like to know whether there is a way LyX won't break up > paragraphs between pages. > > A cursory web search showed that older versions of LyX had a window to > specify paragraph breaks, but I can't seem to find it in the current > version. Perhaps something like this can help a bit: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopagebrk In the case you need it just once, you can try to set penalty at the particular place sufficiently high. For more info check Knuth's TeX book, stuff on penalty (google term: tex book pdf). Best, Peter. -- Peter Novak, p...@aronde.net, http://peter.aronde.net/ signature.asc Description: Digital signature
Re: Layouts vs cls file definition (was: Lyx .layout language for nagauth.cls)
Hello Alex,
> I propose one of two
> solutions: isn't a way to get layout files automatically from cls
> file definitions, if this is too overwhelming I can handle with just
> the basics and then add manually the rest for the first glance (a
> python script would be nice, suggested name "cls2layout.py"); second
> solution could be that lyx can actually read the cls file as an
> option to the layout file, this is not in lyx philosophy but why
> not? It would be helpful in some specific cases like this which is
> used a lot. Probably this is solved someway or someone has already
> found a solution so it would be nice if it is published here, I'm
> open at suggestions.
This would be extremely difficult to do. Realize that most non-trivial
packages do not rely on plain LaTeX, but rather implement large amounts
of their functionality in plain TeX and things are much messier down
there.
Just consider:
1.- it simply is not the case that you can just parse out
\newcommand, \renewcommand and newenvironmennt definitions and you
are fine. In fact, most of the time you are not. What you need to
consider are all the \def definitions, but that's not the way to do
it. Perhaps for the default LaTeX packages yes, but not the custom
ones of journals and various publishers. In fact, many of those I
saw so far were implemented so that they work for the publisher,
they are not meant to tinker with too much.
2.- TeX (and hence LaTeX) does not facilitate specification of a public
interface of a package. In fact everything (i.e., every symbol
defined in any package) is public - hence all the issues with
namespace clashes between packages. So there's no easy way to say
what should be articulated in the resulting layout.
3.- for many non-trivial packages, the parsing of arguments (e.g.,
starred environments) is done dynamically. Without interpreting the
underlying TeX code you wouldn't be able to find out what the
arguments of a command, nor their semantics and layout ([] vs. {})
should be.
... and we did not dive yet into all the options, and configuration
directives various packages enable (e.g., KOMA packages are very
rich and complex in this respect).
All this could be helped by having package implementors annotated
commands, but well, it's already too late (30+ years too late?) to
complain about that one, right? We have thousands of packages existing
already. Another idea might me to parse the cls file and then decide
what is important and how it is used by searching the web for tex files
with that document class and automatically extract/learn from those what
is the package interface. Well, good luck with that one...
So to sum up: in my opinion, manual layout file creation is the
easiest and most reliable method to rely upon.
My 2 cents.
Best,
Peter.
--
Peter Novak, p...@aronde.net, http://peter.aronde.net/
signature.asc
Description: Digital signature
Re: inability to compile from bio.cls
Hello Jim, On Wed, Jul 04, 2012 at 11:29:29AM +0100, Jim Maas wrote: > Another small issue. When I run lyx from terminal it compiles and > then shows me the pdf just fine. When I run lyx directly from icon > on ubuntu linux screen, it compiles ok but gives a "file not found" > error when I try to view the pdf. Any suggestions on how to > fix/correct this? Must be something to do with the paths where lyx > stores the pdf? When you are running from the terminal, your .bashrc (or the resource file of whatever other shell you use) was loaded and your environment is set accordingly. E.g., your localtexmf tree can be found. Unlike that, when you run LyX from an X session, your .bashrc where you possibly set LOCALTEXMF, or alike was not loaded and therefore often your files won't compile properly resulting in errors like you describe. To tackle that, I put this into my ~/.xsessionrc: # include .bashrc if it exists if [ -f "$HOME/.bashrc" ]; then . "$HOME/.bashrc" fi That takes into the scope all the settings you might have set locally, such as $TEXMFLOCAL and related settings. Hopefully this helps a bit. Peter. -- Peter Novak, p...@aronde.net, http://peter.aronde.net/ signature.asc Description: Digital signature
Theorists labbook package - comments and help solicitation
Hello LyX users and developers, my name is Peter Novak and since around 2001 I am a (passionate) user of LyX (as also documented by my bug reports and feature requests at http://www.lyx.org/trac/search?q=walkmanyi), though I did not read the LyX-users mailing lists till now. To scratch one of many itches of my professional life, I created an unpolished quick-hack LaTeX/LyX package aimed at creation and manipulation of lab books for theorists. I include a motivation for writing the package below and discuss it in the accompanying notes to the package accessible from here: http://www.aronde.net/theolabbook.tar.gz (readme.pdf/lyx) file. Hereby I would like to solicit comments from the LyX users community, which includes also many research professionals, especially in applied mathematics and computer science, which is what I care for myself. The best outcome of this announcement for me would be getting help with improvements of the package - these are also briefly discussed in the readme notes to the package. Below, I am including the motivation for writing the package, which (hopefully) illuminates the problem I want to solve. In the case somebody finds this kind of work useful, I would be happy to give back something to the LyX community as I am definitely grateful to the LyX team for providing this great tool I rely on in my every-day work since many years. Best regards, Peter. *** Motivation Keeping a research lab-book is a daily bread for many researchers, such as experimental physicists. It helps them to keep track of their experiments, equipment, results, as well as capture their ideas about the stuff they work on. Typically a researcher, or a team, keeps one lab-book per project. This suits the typical workflow of experimental research, where the evolution of a project can be captured as a (more, or less) linear stream of notes in a lab book. Scientists in more theoretical disciplines, such as (applied) mathematics, or in computer science often deal with several intertwined and related, yet distinct topics at once. In a consequence the evolution of their thoughts from inception to a finished paper is often rather non-linear, rather meandering stream of ideas and notes, which are difficult to order linearly before the idea/project is ripe enough and finally “clicks in”. Yet, due to this non-linearity, researchers in theoretical fields are perhaps even more in a need to capture their research notes so that they do not get lost. There is definitely a need for flexible tools and workflows to help theorists capture, organize and expose their ideas and research notes. Theolabbook is an attempt to solve this problem for users which center their daily life around TeX related tools, which are especially useful when one deals with mathematics. The central requirements driving the development of the theolabbook package are the following: 1.- notes should be media-rich in terms to the extent TeX allows. That is, should easily include math, pictures, figures, etc.; 2.- notes can be scribbled in a linear fashion, their order should be irrelevant; 3.- the package should provide tools for rapid and simple organization and re-organization of the set of notes, result of which is primarily a document, the lab-book instance; 4.- the editing of the notes should be as simple as possible, yet as good as possible. This is a no-brainer, LyX is the editor of choice; 5.- the package should facilitate also publishing of the notes on the web to support the open notebook research (https://en.wikipedia.org/wiki/Open_notebook_science). As of publishing this document, the package implements requirements 1-3 (supported only in Unix environments, for reasons, see the internal philosophy of the package in the readme document), to a large extent also 4 and completely lacks support for 5. By publishing the package as is together with the readme ntroductory text, my hope is to firstly, receive comments, suggestions, and criticism from interested LyX users; and secondly, solicit help with improvements, improving upon the implementation of the requirement 4 and working out 5. The rest of the readme document is structured as follows: after a brief discussion of related work and existing tools for the problem of capturing and organization of a non-linear stream of notes, I explain the guts of the theolabbook package, provide a step-by-step installation instructions, explain included examples and finally discuss its shortcomings and points where I need help from others. *** Related work The observation of non-linearity of research notes in many disciplines is of course a well known issue. Some of the popular solutions to the problem is the use of wikis and blogs (see https://en.wikipedia.org/wiki/Open_research, https://en.wikipedia.org/wiki/Open_notebook_science). While blogs facilitate publication and open discussion of research
