Re: IBM Selectric
Andrew Criswell wrote: > Does anyone know of a style file that mimics IBM selectric completely or > how I can convert my LyX file to that style? I don't know how that looked, but the memoir class has an option "ms" which emulates typewriter. There is no memoir layout yet in the distribution, but I have send one two this list a few days ago. Jürgen.
Re: Clue needed: installing new package
On Fri, Sep 19, 2003 at 07:39:03PM +0200, Juergen Spitzmueller wrote:
> > Please pass me a clue here.
> #% Do not delete the line below; configure depends on this
> # \DeclareLaTeXClass{memoir}
> # Memoir textclass definition file (poor man's version).
> # Author: Jürgen Spitzmüller <[EMAIL PROTECTED]>
>
> # Input general definitions
> Input stdclass.inc
>
> # Global parameters.
> Sides 2
> PageStyle Headings
>
> # There is no abstract environment in book.cls
> NoStyle Abstract
>
> # a few changes to the bibliography
> Style Bibliography
> TopSep 4
> LabelString Bibliography
> # label font definition
> LabelFont
> SeriesBold
> Size Huge
> EndFont
> End
>
> ClassOptions
> FontSize9|10|11|12|14|17
> end
Should this be added to lib/layouts?
Andre'
Re: PDF Encryption for LyX Request
Marc Jeffrey Driftmeyer wrote: > I am writing several works, from a couple novels to technical documents > and would really love the ability to have an Inspector View (ala OS X > Cocoa) to set PDF encryption for final output. > > Is this a subproject being considered yet? A search of CTAN suggests that you can do it already using LaTeX. Find it at: http://www.ctan.org/tex-archive/help/Catalogue/entries/pdfcrypt.html Here is the original announcement, explaining how to use it: http://www.tug.org/pipermail/pdftex/2001-August/001483.html Alternatively, there appear to be a bunch of utilities out there to encrypt an existing pdf doc. To use one of these, use the converter stuff to: 1. Define a new format pdfencrypted 2. Define a converter from your favourite flavour of pdf to pdfencrypted. -- Angus
Re: Clue needed: installing new package
Andre Poenitz wrote: > Should this be added to lib/layouts? IMO yes. I have sent an enhanced version to the devel list. Jürgen.
Re: button tools
On Sat, Sep 20, 2003 at 12:31:58PM -0400, William O. Bray wrote:
> find that I often use this as well as the insert matrix dialog and it would
> be convenient to reach these without going through the math panel.
> It is easy to add buttons for \sum or \int.
Apart from what John said:
You can add pairs of matching delimiters by simply typing M-m (, M-m [,
M-m {.
Andre'
--
Those who desire to give up Freedom in order to gain Security, will not have,
nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
Re: Clue needed: installing new package
On Mon, Sep 22, 2003 at 09:58:47AM +0200, Juergen Spitzmueller wrote: > Andre Poenitz wrote: > > Should this be added to lib/layouts? > > IMO yes. I have sent an enhanced version to the devel list. Done for the lyx-devel part. Try to stick to LyX's indentation rules (tab for indentation, spaces for in-line-adjustments) and provide a ChangeLog entry next time. I don't have write access to lyxdoc, so ask someone else for the second part. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
Re: Clue needed: installing new package
Andre Poenitz wrote: > Done for the lyx-devel part. Try to stick to LyX's indentation rules > (tab for indentation, spaces for in-line-adjustments) and provide a > ChangeLog entry next time. Thanks. I would have written a ChangeLog entry before applying (myself). Thanks for doing it anyway. > I don't have write access to lyxdoc, so ask someone else for the second > part. As I understand, we have only one dosumentation tree, so apllying would not make sense unless the layout will also be added to 1.3. Jürgen.
Re: Clue needed: installing new package
Juergen Spitzmueller wrote: >> I don't have write access to lyxdoc, so ask someone else for the second >> part. > > As I understand, we have only one dosumentation tree, so apllying would > not make sense unless the layout will also be added to 1.3. What makes you think that? http://www.lyx.org/cgi-bin/viewcvs.cgi/lyxdoc/?only_with_tag=lyx-1_3_2 -- Angus
Re: Clue needed: installing new package
Andre Poenitz schrieb:
On Fri, Sep 19, 2003 at 07:39:03PM +0200, Juergen Spitzmueller wrote:
Please pass me a clue here.
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass{memoir}
# Memoir textclass definition file (poor man's version).
# Author: Jürgen Spitzmüller <[EMAIL PROTECTED]>
# Input general definitions
Input stdclass.inc
# Global parameters.
Sides 2
PageStyle Headings
# There is no abstract environment in book.cls
NoStyle Abstract
how would you control the different styles of memoir?
book - article - ...
If you write the layout file in this way, then you have
chapters with the article option, too. And so the
counting of the sections is wrong.
Herbert
Re: Clue needed: installing new package
Angus Leeming wrote: > What makes you think that? I was just gessing (wrong, obviously). > http://www.lyx.org/cgi-bin/viewcvs.cgi/lyxdoc/?only_with_tag=lyx-1_3_2 I see. What is the difference between lyxdoc-1_3_2 and lyxdoc -BRANCH_1_3_X? The latter is the current stable branch while the former is the documentation of the 1.3.2 release? Thanks, Jürgen.
Re: Clue needed: installing new package
Herbert Voß wrote:
> how would you control the different styles of memoir?
> book - article - ...
> If you write the layout file in this way, then you have
> chapters with the article option, too. And so the
> counting of the sections is wrong.
from meman.tex:
\item[\Lopt{article}] typesetting simulates the \Lclass{article} class,
but the \cmd{\chapter} command is not disabled.
Chapters\index{chapter} do not start a new page and chapter
headings\index{heading!chapter} are typeset
like a section heading\index{heading!sections}. The numbering of
figures\index{figure}, etc., is continuous
and not per chapter. However, a \cmd{\part} command still puts
its heading\index{heading!part} on a page by itself.
So I understand that it is intended to have chapters even with the article
option. Anyway, feel free to improve the layout (it's in CVS now).
Jürgen.
Re: PDF Encryption for LyX Request
Angus Leeming schrieb: Marc Jeffrey Driftmeyer wrote: I am writing several works, from a couple novels to technical documents and would really love the ability to have an Inspector View (ala OS X Cocoa) to set PDF encryption for final output. Is this a subproject being considered yet? A search of CTAN suggests that you can do it already using LaTeX. Find it at: http://www.ctan.org/tex-archive/help/Catalogue/entries/pdfcrypt.html this is totally out of date. There is no more the option to use pdfcrypt. From the news: - The extensions for pdf encryption have been removed, since they make the pdfTeX code overly complex. Those needing pdf encryption are encouraged to produce a standalone program for encrypting pdfs. Herbert
Re: Clue needed: installing new package
Juergen Spitzmueller schrieb:
Herbert Voß wrote:
how would you control the different styles of memoir?
book - article - ...
If you write the layout file in this way, then you have
chapters with the article option, too. And so the
counting of the sections is wrong.
from meman.tex:
\item[\Lopt{article}] typesetting simulates the \Lclass{article} class,
but the \cmd{\chapter} command is not disabled.
Chapters\index{chapter} do not start a new page and chapter
headings\index{heading!chapter} are typeset
like a section heading\index{heading!sections}. The numbering of
figures\index{figure}, etc., is continuous
and not per chapter. However, a \cmd{\part} command still puts
its heading\index{heading!part} on a page by itself.
So I understand that it is intended to have chapters even with the article
sure, I never said, that there are no chapters.
I meant, that it is not a good way to have different
counting of section titles in LyX gui and output.
Herbert
Re: Clue needed: installing new package
Herbert Voß wrote: > sure, I never said, that there are no chapters. > I meant, that it is not a good way to have different > counting of section titles in LyX gui and output. You lost me. If I have a memoir document with article option, an I use section without a chapter, I get 0.1 first section bla 0.2 second section bla both in LyX and dvi. Can you send an example please? Jürgen.
Re: Clue needed: installing new package
Juergen Spitzmueller wrote: > Angus Leeming wrote: >> What makes you think that? > > I was just gessing (wrong, obviously). > >> http://www.lyx.org/cgi-bin/viewcvs.cgi/lyxdoc/?only_with_tag=lyx-1_3_2 > > I see. What is the difference between lyxdoc-1_3_2 and lyxdoc > -BRANCH_1_3_X? The latter is the current stable branch while the former > is the documentation of the 1.3.2 release? That is my understanding. lyxdoc-BRANCH_1_3_X is a true branch from the cvs tree. Its position evolves as bugs are fixed. The lyxdoc-1_3_2 specifies a point on this branch. Its position is immutable. -- Angus
Re: Clue needed: installing new package
Juergen Spitzmueller schrieb: Herbert Voß wrote: sure, I never said, that there are no chapters. I meant, that it is not a good way to have different counting of section titles in LyX gui and output. You lost me. If I have a memoir document with article option, an I use section without a chapter, I get 0.1 first section bla 0.2 second section bla both in LyX and dvi. huh, now I see, my fault. I thought, that the counting of the sections is also conrinously ... sorry, Herbert
Re: Clue needed: installing new package
Angus Leeming wrote: > That is my understanding. lyxdoc-BRANCH_1_3_X is a true branch from the cvs > tree. Its position evolves as bugs are fixed. The lyxdoc-1_3_2 specifies a > point on this branch. Its position is immutable. Thanks for clarification, Angus. Jürgen.
xfig + lyx
My apologies if this mail gets posted twice, but I sent the original
yesterday and I haven't seen it arrive yet, so here's trying again.
I seem to be having a rather difficult time getting xfig and lyx to play
nicely together when exporting pstex/pstex_t files from xfig. I'm sure
I'm doing something wrong, but I can't seem to figure out what.
Here's the details:
tetex-2.0.2 (gentoo tetex-2.0.2-r1 package)
lyx-1.3.2 (gentoo lyx-1.3.2-r1 package)
xfig-3.2.4 (gentoo xfig-3.2.4-r1 package)
The error I get is:
Undefined control sequence.
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
The lyx file is:
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Standard
Here's some generic text, followed by a ps figure.
\layout Standard
\begin_inset Float figure
wide false
collapsed false
\layout Caption
inserted pstext graphic
\layout Standard
\begin_inset Graphics
filename /home/grant/class/chem330/2003/hotcold.pstex
\end_inset
\end_inset
\layout Standard
More generic text, followed by a figure float that includes my pstext_t
file:
\layout Standard
\begin_inset Float figure
wide false
collapsed false
\layout Caption
included pstext_t
\layout Standard
\begin_inset Include
\input{/home/grant/class/chem330/2003/hotcold.pstex_t}
preview false
\end_inset
\end_inset
\layout Standard
All done!
\the_end
The pstex_t file is:
\begin{picture}(0,0)%
\includegraphics{/home/grant/class/chem330/2003/hotcold.pstex}%
\end{picture}%
\setlength{\unitlength}{3947sp}%
%
\begingroup\makeatletter\ifx\SetFigFont\undefined%
\gdef\SetFigFont#1#2#3#4#5{%
[EMAIL PROTECTED]
\fontfamily{#3}\fontseries{#4}\fontshape{#5}%
\selectfont}%
\fi\endgroup%
\begin{picture}(2574,1074)(1114,-1348)
\put(1276,-1186){\makebox(0,0)[lb]{\smash{{\SetFigFont{12}{14.4}{\rmdefault}{\mddefault}{\updefault}{\color[rgb]{0,0,0}$E_1,V_1,n_1$}%
\end{picture}%
The pstex file is fairly lengthy, but if you really want to see it you
can snag it from "http://www.gentoo.org/~g2boojum/hotcold.pstex";.
Any advice gratefully accepted!
Thanks,
Grant Goodyear
--
Grant Goodyear The Secrets of Physics:
Dept. of Chemistry 1. Add zero.
Clemson University 2. Multiply by one.
Clemson, SC 29617 3. Expand in a Taylor series
(864) 656-7702 4. Integrate by parts.
e-mail: [EMAIL PROTECTED] 5. Fourier transform.
Re: xfig + lyx
Grant Goodyear wrote: > My apologies if this mail gets posted twice, but I sent the original > yesterday and I haven't seen it arrive yet, so here's trying again. > > I seem to be having a rather difficult time getting xfig and lyx to play > nicely together when exporting pstex/pstex_t files from xfig. I'm sure > I'm doing something wrong, but I can't seem to figure out what. > > Here's the details: > tetex-2.0.2 (gentoo tetex-2.0.2-r1 package) > lyx-1.3.2 (gentoo lyx-1.3.2-r1 package) > xfig-3.2.4 (gentoo xfig-3.2.4-r1 package) > > The error I get is: > > Undefined control sequence. > I've seen this before and you aren't going to like the answer. It's almost certain that you have indeed got an extra '}' in one of your snippets of latex text. Try editing the .fig file manually. -- Angus
Re: xfig + lyx
On Mon, Sep 22, 2003 at 09:01:36AM -0400, Grant Goodyear wrote:
> My apologies if this mail gets posted twice, but I sent the original
> yesterday and I haven't seen it arrive yet, so here's trying again.
>
> I seem to be having a rather difficult time getting xfig and lyx to play
> nicely together when exporting pstex/pstex_t files from xfig. I'm sure
> I'm doing something wrong, but I can't seem to figure out what.
>
> Here's the details:
> tetex-2.0.2 (gentoo tetex-2.0.2-r1 package)
> lyx-1.3.2 (gentoo lyx-1.3.2-r1 package)
> xfig-3.2.4 (gentoo xfig-3.2.4-r1 package)
>
> The error I get is:
>
> Undefined control sequence.
>
>
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.
Make sure to put a '\usepackage{color}' in your preamble, or use
'default color', not 'black' in XFig or simply define a
\def\color[rgb]#1{} macro to gobble the \color information xfig puts
there:
> \begin{picture}(0,0)%
> \includegraphics{/home/grant/class/chem330/2003/hotcold.pstex}%
> \end{picture}%
> \setlength{\unitlength}{3947sp}%
> %
> \begingroup\makeatletter\ifx\SetFigFont\undefined%
> \gdef\SetFigFont#1#2#3#4#5{%
> [EMAIL PROTECTED]
> \fontfamily{#3}\fontseries{#4}\fontshape{#5}%
> \selectfont}%
> \fi\endgroup%
> \begin{picture}(2574,1074)(1114,-1348)
> \put(1276,-1186){\makebox(0,0)[lb]{\smash{{\SetFigFont{12}{14.4}{\rmdefault}{\mddefault}{\updefault}{\color[rgb]{0,0,0}$E_1,V_1,n_1$}%
^^
>
> \end{picture}%
Andre'
--
Those who desire to give up Freedom in order to gain Security, will not have,
nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
Re: xfig + lyx
Grant Goodyear schrieb:
The error I get is:
Undefined control sequence.
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
your code is okay, I have no problems running it with LaTeX.
So I can only guess, what happens.
Do you have a \usepackage{graphicx} in the preamble?
Herbert
p.s.: your xfig image is a five-liner with pstricks.
http://www.pstricks.de
Re: xfig + lyx
Herbert Voß schrieb:
your code is okay, I have no problems running it with LaTeX.
So I can only guess, what happens.
Do you have a \usepackage{graphicx} in the preamble?
sorry, it should be \usepackage{color}
Herbert
Shortcut-key expansion
Is it possible within LyX to define "hot keys" (e.g., alt-e) which will, when invoked, enter a string of text into the document? For example, in my book I write the string, "environmental impact assessment" many, many times. It would be nice to press a couple of keys and get the same result in the document. TIA, Rich Dr. Richard B. Shepard, President Applied Ecosystem Services, Inc. (TM) 2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A. + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com http://www.appl-ecosys.com/
Re: Shortcut-key expansion
Rich Shepard wrote: > Is it possible within LyX to define "hot keys" (e.g., alt-e) which will, > when invoked, enter a string of text into the document? For example, in my > book I write the string, "environmental impact assessment" many, many > times. It would be nice to press a couple of keys and get the same result > in the document. Yes. Look at Customization.lyx, section 3.3 Bindings. In a nutshell, you'll have to bind the command "self-insert environmental impact assessment" to some key. You achieve this by adding to your bind file a line like: \bind "M-i e" "self-insert environmental impact assessment" Alfredo
Re: "Path to the lyx file cannot contain spaces"
James Frye <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]: > On Thu, 18 Sep 2003, Bruce wrote: > >> I get this message when try to preview a file that (suprise) is in a >> directory that has spaces in its name. >> >> Not that this is a huge deal, I'm just curious... why is this? > > There's an obvious answer: file and directory names should NEVER contain > spaces. If you somehow encounter one that does, it is most likely a bug > of some sort, and not a valid file. > > James > > > Sounds right for *nix, but spaces in paths are a way of life in the Windoze world (not sure about Macs, but I think they're legal there, too). -- Paul
Re: Shortcut-key expansion
Alfredo Braunstein wrote: > \bind "M-i e" "self-insert environmental impact assessment" Of course, if you want it to be bound to alt-e, replace "M-i e" above by "M-e". Alfredo
Index creation fails
Hi,
I just recently started having a problem generating an index using LyX.
This was working just fine at one point, however now it refuses to
produce an index.
I was using LyX 1.1.6fix3. Once the problem started occuring I decided
to finally upgrade to the latest version, 1.3.2 which didn't resolve my
problem.
After exporting the LyX document to Tex I checked through to make sure
the necessary parameters were in the file and indeed '\makeindex' was
there, the typical index entry looked like 'text\index{item1} text' and
found at the end of my document was my index '\printindex{}'.
I then ran makeindex by hand using the flags '-p -s', which I read is
what LyX uses by default and got the following results:
[EMAIL PROTECTED] IPS-1.5]$ makeindex -p -s IPS-1.5.tex
This is makeindex, version 2.13 [07-Mar-1997] (using kpathsea).
Scanning input file IPS-1.5.tex...done (0 entries accepted, 11062 rejected).
Nothing written in IPS-1.5.ind.
Transcript written in IPS-1.5.ilg.
I have makeindex installed on a RH 7.2 system from the tetex package
(tetex-1.0.7-38.3).
The only changes I can think of that may have recently changed was
possibly an updated tetex package, which may have included an update
makeindex. However I am uncertain of this.
Thanks,
-Nick
Re: "Path to the lyx file cannot contain spaces"
On Monday 22 September 2003 13:40, Paul A. Rubin wrote: > Sounds right for *nix, but spaces in paths are a way of life in the > Windoze world (not sure about Macs, but I think they're legal there, > too). Any software which allows commands with arguments has to have some way of separating commands and arguments from each other. By analogy with English (and many other languages) almost all software systems which are text-based use spaces as separators. Unix and similar systems use spaces as separators, but often can accept file and directory names with spaces by enclosing them in double quotes. Unfortunately, many programs running under these systems use scripts which do not enclose file names in quotes, so they break when they encounter such names. LaTeX is obviously such a program. As far as I know, Windows is the only significant operating system which allows spaces in file and directory names. This is in keeping with its design as a totally graphical operating system, where a command line should never be needed. Les
Re: Shortcut-key expansion
On Mon, 22 Sep 2003, Alfredo Braunstein wrote: > > \bind "M-i e" "self-insert environmental impact assessment" > > Of course, if you want it to be bound to alt-e, replace "M-i e" above by > "M-e". Alfredo, Thanks very much. I must have missed a step because it's not working as intended. First, I copied /usr/local/share/lyx/bind/emacs.bind to ~/.lyx/bind/. Second, I added the bind command near the top of that file. Third, exited LyX and shut it down. Then I re-invoked the application and reloaded the file. Still, when I press alt-e I get the edit menu. What have I missed? Rich Dr. Richard B. Shepard, President Applied Ecosystem Services, Inc. (TM) 2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A. + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com http://www.appl-ecosys.com/
Re: Shortcut-key expansion
Rich Shepard wrote: > Still, when I press alt-e I get the edit menu. > > What have I missed? Unfortunately, you cannot use any key which is already taken by a menu shortcut (the underlined letters in the menus). So you'll have to choose another key. Alfredo
Re: Shortcut-key expansion
On Mon, Sep 22, 2003 at 09:36:22PM +0200, Alfredo Braunstein wrote: > > Still, when I press alt-e I get the edit menu. > > Unfortunately, you cannot use any key which is already taken by a menu > shortcut (the underlined letters in the menus). So you'll have to choose > another key. Or edit the menu file (default.ui) to remove the E binding "Edit|E" -> "Edit" regards john -- Khendon's Law: If the same point is made twice by the same person, the thread is over.
Re: Shortcut-key expansion
Alfredo Braunstein <[EMAIL PROTECTED]> writes: > Rich Shepard wrote: > > > Still, when I press alt-e I get the edit menu. > > > > What have I missed? > > Unfortunately, you cannot use any key which is already taken by a menu > shortcut (the underlined letters in the menus). If you want to use a key that is taken by a menu shortcut, copy lyx-dir/lyx/ui/default.ui to ~/.lyx/ui/default.ui and edit it to take out the offending shortcut, e.g., change Submenu "Edit|E" "edit" to Submenu "Edit" "edit" Then restart LyX. -- Ronald Florence www.18james.com
Re: "Path to the lyx file cannot contain spaces"
Paul A. Rubin wrote: > Sounds right for *nix, but spaces in paths are a way of life in the > Windoze world (not sure about Macs, but I think they're legal there, > too). And your point is? LyX could happily support spaces in paths. However, it farms out all the 'hard' work to other utilities. Specifically, to farms out the typesetting of the printed page to TeX. TeX can't handle spaces in paths. We do debate occasionally whether we should _force_ you all to use a temp directory for all the temporary files generated during the creation of a dvi,ps or pdf file. Such a requirement _would_ enable you to visualise your output because we could mangle all file names. If the path of the tmp directory did not contain spaces that is. However, you'd still run into problems when you exported the latex file and gave it to a co-worker. So. There is no obvious work around for a TeX limitation. Don't use spaces in file paths if you want LyX to work as you'd like. -- Angus
Re: Shortcut-key expansion
On Mon, 22 Sep 2003, Alfredo Braunstein wrote: > Unfortunately, you cannot use any key which is already taken by a menu > shortcut (the underlined letters in the menus). So you'll have to choose > another key. Of course! Rich Dr. Richard B. Shepard, President Applied Ecosystem Services, Inc. (TM) 2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A. + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com http://www.appl-ecosys.com/
Re: "Path to the lyx file cannot contain spaces"
Angus Leeming <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]: > Paul A. Rubin wrote: >> Sounds right for *nix, but spaces in paths are a way of life in the >> Windoze world (not sure about Macs, but I think they're legal there, >> too). > > And your point is? That those of us using Windows (not all voluntarily, I might add) do have to make accommodations (such as renaming directories, or adding symbolic links) to use LyX (and, for that matter, most any software ported from Unix-like systems). The generalization of the prior post that "file and directory names should NEVER contain spaces" is a bit draconian in the Windows world, if not inapt. After all, the operating system is geared toward having all programs installed in "\Program Files" and most of your documents in "My Documents". In fact, in some institutional settings, you may be required to follow those guidelines (either to ensure that your files are backed up, or to keep the network police happy). > > LyX could happily support spaces in paths. However, it farms out all > the 'hard' work to other utilities. Specifically, to farms out the > typesetting of the printed page to TeX. TeX can't handle spaces in > paths. > > We do debate occasionally whether we should _force_ you all to use a > temp directory for all the temporary files generated during the > creation of a dvi,ps or pdf file. Such a requirement _would_ enable > you to visualise your output because we could mangle all file names. > If the path of the tmp directory did not contain spaces that is. Wouldn't there still be a problem with spaces in the path to the source files? > However, you'd still run into problems when you exported the latex > file and gave it to a co-worker. > > So. There is no obvious work around for a TeX limitation. Don't use > spaces in file paths if you want LyX to work as you'd like. Since I'm using the Cygwin port, my solution is to put symlinks in my Cygwin home directory pointing to wherever in the "My Documents" subtree a particular project is parked. Don't get me wrong, I'm very happy with LyX, and the space-in-the-path issue is not a big deal to me. It does, however, seem to come up fairly regularly in the group. Just out of curiosity, have you given any consideration to escaping spaces in paths when passing them to external apps (as in /My\ Documents/Path\ to\ Project/whatever)? -- Paul
Re: "Path to the lyx file cannot contain spaces"
On Mon, 22 Sep 2003, Paul A. Rubin wrote: > Angus Leeming <[EMAIL PROTECTED]> wrote in > > That those of us using Windows (not all voluntarily, I might add) do have > to make accommodations (such as renaming directories, or adding symbolic > links) to use LyX (and, for that matter, most any software ported from > Unix-like systems). The generalization of the prior post that "file and > directory names should NEVER contain spaces" is a bit draconian in the > Windows world, if not inapt. After all, the operating system is geared > toward having all programs installed in "\Program Files" and most of your > documents in "My Documents". Which I suppose was really my point: The universe in which I think most Lyx users spend most of their time is one in which simple, sensible software is a desirable goal. The rule about filenames not containing spaces is there for a reason (just as for instance there are rules about which side of the road you drive on), and it was a rule in all operating systems I know of for a long time before there ever was a Windows. If Microsoft chooses to break the rule, why should we in the rest of the world be expected to do a lot of work to compensate for their arrogance? A simple error message is IMHO quite sufficient :-) For that matter, even in Windows the real filenames don't contain spaces. Rather, each file has a name which follows the 8.3 rule, and a text label that can be used instead. That label may contain spaces (and be quite long), but the filename doesn't. Thus for instance the "Program Files" directory is really named "PROGRA~1", and people forced to follow Windows conventions can easily use that instead. James
\sectionmark
Hello LyX-List,
In a document I use "fancy" pagestyle and I want the chapters and
sectiontitles to be printed in short form in the header, so some of the
older E-mails tell that the command needed is:
\sectionmark{abc}
and it works for all the pages where no new section is started. But on
this page the short chapter-title but the long (original) section-title
is displayed in the header; so another E-mail tells that the pagestyle
ist set to plain at the beginning of new chapters - is it the same with
beginnings of new sections, and: is this the problem? - can I change
this?
-Kai-
--
Kai Johannes Keller <[EMAIL PROTECTED]>
Re: "Path to the lyx file cannot contain spaces"
On Mon, Sep 22, 2003 at 04:18:38PM -0700, James Frye wrote: > Which I suppose was really my point: The universe in which I think most > Lyx users spend most of their time is one in which simple, sensible > software is a desirable goal. The rule about filenames not containing > spaces is there for a reason (just as for instance there are rules about > which side of the road you drive on) There is no such rule in UNIX. It's a LaTeX bug. That simple. > For that matter, even in Windows the real filenames don't contain spaces. > Rather, each file has a name which follows the 8.3 rule, and a text label > that can be used instead. That label may contain spaces (and be quite > long), but the filename doesn't. Thus for instance the "Program Files" > directory is really named "PROGRA~1", and people forced to follow Windows > conventions can easily use that instead. This is not how things work. "PROGRA~1" is most definitely NOT the "real filename". john -- Khendon's Law: If the same point is made twice by the same person, the thread is over.
Re: Shortcut-key expansion
On Mon, 22 Sep 2003, Rich Shepard wrote: > On Mon, 22 Sep 2003, Alfredo Braunstein wrote: > > > Unfortunately, you cannot use any key which is already taken by a menu > > shortcut (the underlined letters in the menus). So you'll have to choose > > another key. > See this URI for tips on creating bindings http://wiki.lyx.org/pmwiki.php/Tips/CommandSequences I put a note about this subject here: http://wiki.lyx.org/pmwiki.php/Tips/BlockedKeyboardShortcuts /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: "Path to the lyx file cannot contain spaces"
On 2003-09-22, 23:18 GMT, James Frye wrote: > For that matter, even in Windows the real filenames don't contain > spaces. Rather, each file has a name which follows the 8.3 rule, and > a text label that can be used instead. That label may contain spaces > (and be quite long), but the filename doesn't. Thus for instance the > "Program Files" directory is really named "PROGRA~1", and people > forced to follow Windows conventions can easily use that instead. I think that you are here rather unfair towards newer versions of Windows. My wife has WindowsXP (now working hard to switch to Linux) and it seems that now they have true spaces in filesnames -- PROGRA~1 seems to be gone forever. Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Re: One for the LaTeX masters
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Guys, the attached file works well enough, but it's rather
Angus> inelegant. I have defined a macro, so:
Angus, I am not sure what was the concusion of this thread, but let me
propose a \DoOrWarn variant:
%% Do command #1 if file #2 exists, else print a warning
\newcommand{\DoOrWarn}[2]{
\IfFileExists{#2}{#1{#2}}{\warnNotFound{#2}}
}
%% Input the file if it exists, else print a warning
\newcommand{\verbatiminputOrWarn}[1]{%
\DoOrWarn{\verbatiminput}{#1}
}
%% Input the file if it exists, else print a warning
\newcommand{\verbatiminputStarOrWarn}[1]{%
\DoOrWarn{\verbatiminput*}{#1}
}
As you can see, \verbatiminputOrWarn and are now so trivial that they
should be removed \verbatiminputStarOrWarn, and the only preamble bit
would be \warnNotFound and \DoOrWarn (the name being arbitrary).
JMarc
Re: "Path to the lyx file cannot contain spaces"
On Mon, Sep 22, 2003 at 07:35:55PM -0400, Matej Cepl wrote: > On 2003-09-22, 23:18 GMT, James Frye wrote: > > For that matter, even in Windows the real filenames don't contain > > spaces. Rather, each file has a name which follows the 8.3 rule, and > > a text label that can be used instead. That label may contain spaces > > (and be quite long), but the filename doesn't. Thus for instance the > > "Program Files" directory is really named "PROGRA~1", and people > > forced to follow Windows conventions can easily use that instead. > > I think that you are here rather unfair towards newer versions of > Windows. My wife has WindowsXP (now working hard to switch to Linux) and > it seems that now they have true spaces in filesnames -- PROGRA~1 seems > to be gone forever. > Really? I am running Windows XP and Progra~1 *does* work. Have you tried it? C:\cygwin\home\Kayvan>dir c:\progra~1\tcl dir c:\progra~1\tcl Volume in drive C has no label. Volume Serial Number is 501B-4DAE Directory of c:\progra~1\tcl 12/19/2001 01:55 AM . 12/19/2001 01:55 AM .. 12/19/2001 01:54 AM bin 12/19/2001 01:54 AM doc 12/19/2001 01:54 AM include 12/19/2001 01:55 AM15,048 INSTALL.LOG 12/19/2001 01:54 AM lib 08/08/2000 02:59 PM 2,272 license.txt 08/08/2000 02:59 PM 5,613 Readme.txt 06/21/1999 11:21 AM 245,616 UNWISE.EXE 4 File(s)268,549 bytes 6 Dir(s) 14,768,001,024 bytes free C:\cygwin\home\Kayvan> -- Kayvan A. Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | "crown of her husband" | Robin Gregory (2/28/92)
