On 2/3/25 5:24 PM, Enrico Forestieri wrote:
On Mon, Feb 03, 2025 at 10:15:38PM +, Enrico Forestieri wrote:
commit 9b22c347f9f864e73961d3549dd57ab5f0d595f1
Author: Enrico Forestieri
Date: Mon Feb 3 23:12:41 2025 +0100
Fix check for callstack printing
The code was setting the
On Mon, Feb 03, 2025 at 10:15:38PM +, Enrico Forestieri wrote:
commit 9b22c347f9f864e73961d3549dd57ab5f0d595f1
Author: Enrico Forestieri
Date: Mon Feb 3 23:12:41 2025 +0100
Fix check for callstack printing
The code was setting the cache variable before the check,
so that
a écrit :
> >> > commit 4028eefe6190551c8be96cd451337dea2808742b
> >> > Author: Jean-Marc Lasgouttes
> >> > Date: Mon Feb 25 17:37:06 2019 +0100
> >> >
> >> > Make callstack printing useful and optional
> >> >
> >&
c Lasgouttes
>> > Date: Mon Feb 25 17:37:06 2019 +0100
>> >
>> > Make callstack printing useful and optional
>> >
>> > When callback printing is enabled, link lyx with -rdynamic, so
>that
>> > stacks have LyX symbo
Am Montag, 25. Februar 2019 18:04:10 CET schrieb Jean-Marc Lasgouttes
:
> Le 25/02/2019 à 17:55, Jean-Marc Lasgouttes a écrit :
> > commit 4028eefe6190551c8be96cd451337dea2808742b
> > Author: Jean-Marc Lasgouttes
> > Date: Mon Feb 25 17:37:06 2019 +0100
> >
>
On 2/25/19 12:04 PM, Jean-Marc Lasgouttes wrote:
> Le 25/02/2019 à 17:55, Jean-Marc Lasgouttes a écrit :
>> commit 4028eefe6190551c8be96cd451337dea2808742b
>> Author: Jean-Marc Lasgouttes
>> Date: Mon Feb 25 17:37:06 2019 +0100
>>
>> Make calls
Le 25/02/2019 à 17:55, Jean-Marc Lasgouttes a écrit :
commit 4028eefe6190551c8be96cd451337dea2808742b
Author: Jean-Marc Lasgouttes
Date: Mon Feb 25 17:37:06 2019 +0100
Make callstack printing useful and optional
When callback printing is enabled, link lyx with -rdynamic, so
On 05/28/2015 07:34 AM, Stephan Witt wrote:
commit 0632c91aee255b8bacb7d27a0f4b9efa33c456e2
Author: Stephan Witt
Date: Thu May 28 13:33:56 2015 +0200
Remove leftover from printing support.
Thank you.
rh
Am Sonntag, 9. November 2014 um 09:53:01, schrieb Peter Kuemmel
> > > I try to use the same on cmake side, if nobody (Peter Kümmel?) screams.
> > >
> > > Kornel
> >
> > ping? What about the following (commit message):
> >
> > Cmake build:
> > I try to use the same on cmake side, if nobody (Peter Kümmel?) screams.
> >
> > Kornel
>
> ping? What about the following (commit message):
>
> Cmake build: 'callstack printing' detection.
>
> Instead of depending on compiler
> > >
> > >> commit dc7ef3c81ff6e906c41da5ad40117ab87ac214da
> > >> Author: Jean-Marc Lasgouttes
> > >> Date: Tue Nov 4 23:30:53 2014 +0100
> > >>
> > >> Implement "callstack printing" checking for autotools
s
>>> Date: Tue Nov 4 23:30:53 2014 +0100
>>>
>>> Implement "callstack printing" checking for autotools
>>>
>>> Contrary to cmake, we do not rely on platform/compiler check, but on the
>>> availability of the reauired
> Author: Jean-Marc Lasgouttes
> >> Date: Tue Nov 4 23:30:53 2014 +0100
> >>
> >> Implement "callstack printing" checking for autotools
> >>
> >> Contrary to cmake, we do not rely on platform/compiler check, but on
> >> the
>
Le 05/11/2014 18:15, Kornel Benko a écrit :
Am Dienstag, 4. November 2014 um 23:48:11, schrieb Jean-Marc Lasgouttes
commit dc7ef3c81ff6e906c41da5ad40117ab87ac214da
Author: Jean-Marc Lasgouttes
Date: Tue Nov 4 23:30:53 2014 +0100
Implement "callstack printing" checking for
Am Dienstag, 4. November 2014 um 23:48:11, schrieb Jean-Marc Lasgouttes
> commit dc7ef3c81ff6e906c41da5ad40117ab87ac214da
> Author: Jean-Marc Lasgouttes
> Date: Tue Nov 4 23:30:53 2014 +0100
>
> Implement "callstack printing" checking for autotools
>
&g
I have had a report from a user that he is unable to print from within
2.1.0beta1, though he can do so from within 2.0.6. I suggested he try a
new user, and that did not help. Is there anything else to ask? Can
anyone reproduce?
The error message is the one from the failure of the doExport("
Oops, sorry. Seems I need to fix my Mail settings.
Jürgen
Jürgen Spitzmüller wrote:
> Manveru wrote:
> > The above statement is true only if use design the document for
> > printing, where the space to bind/glue will be added at final prepress
> > stage. In case of docu
Manveru wrote:
> The above statement is true only if use design the document for
> printing, where the space to bind/glue will be added at final prepress
> stage. In case of document printed on laser printer and then manually
> binded the inner margins have to be wider than outer.
F
Richard Heck wrote:
> Alternatively, we can fix the comments package. I did so with paper (and to
> some extent took over maintaining it).
if you know how, then this would be the solution.
pavel
On 07/13/2009 10:29 AM, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Ouch, So we rely on a broken package?
frankly i have no idea whats going on there. if \...@savsf=1 is problem
then i wont commit it.
I don't know. But it really looks like a bad hack.
+1
Jean-Marc Lasgouttes wrote:
Ouch, So we rely on a broken package?
>>>
>>> frankly i have no idea whats going on there. if \...@savsf=1 is problem
>>> then i wont commit it.
>>
>> I don't know. But it really looks like a bad hack.
>
> +1
ok, i withdraw
pavel
Le 13 juil. 09 à 16:15, Jürgen Spitzmüller a écrit :
Am Montag 13 Juli 2009 16:14:31 schrieb Pavel Sanda:
Ouch, So we rely on a broken package?
frankly i have no idea whats going on there. if \...@savsf=1 is problem
then i wont commit it.
I don't know. But it really looks like a bad hack.
Am Montag 13 Juli 2009 16:14:31 schrieb Pavel Sanda:
> > Ouch, So we rely on a broken package?
>
> frankly i have no idea whats going on there. if \...@savsf=1 is problem
> then i wont commit it.
I don't know. But it really looks like a bad hack.
Jürgen
Jürgen Spitzmüller wrote:
> > otherwise i get latex error:
> > "
> > Bad space factor (0).
> > \end{comment}
> >I allow only values in the range 1..32767 here.
> > "
> >
> > i dont know why it happens but i found this solution googling through
> > forums.
>
> Ouch, So we rely on a broken pack
Am Montag 13 Juli 2009 16:10:04 schrieb Pavel Sanda:
> otherwise i get latex error:
> "
> Bad space factor (0).
> \end{comment}
>I allow only values in the range 1..32767 here.
> "
>
> i dont know why it happens but i found this solution googling through
> forums.
Ouch, So we rely on a broken
Jürgen Spitzmüller wrote:
> Makes sense, except for:
>
> > > +AddToPreamble
> > > + \usepackage{comment}
>
> I would rather load the package with
will try
>
> Requirescomment
>
> > > + \...@savsf=1
>
> Why is this needed?
otherwise i get latex error:
"
Bad space factor (0).
\en
Richard Heck wrote:
> Pavel, note that where "comment" appears in that array will determine when
> \usepackage{comments} is output. I don't know if it matters where it goes.
up to know it worked with the documents i tried.
pavel
On 07/13/2009 10:00 AM, Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
ping
Makes sense, except for:
+AddToPreamble
+ \usepackage{comment}
I would rather load the package with
Requirescomment
Yes, that can be done now that we have it in LaTeXFeatures.
Pa
Pavel Sanda wrote:
> ping
Makes sense, except for:
> > +AddToPreamble
> > + \usepackage{comment}
I would rather load the package with
Requirescomment
> > + \...@savsf=1
Why is this needed?
Jürgen
Pavel Sanda wrote:
> Richard Heck wrote:
> > Pavel Sanda wrote:
> >> i see. as there was no feedback i suppose this module will stay locally on
> >> my box, so no additional tweaks needed...
> >>
> >>
> > Actually, I meant to be endorsing it.
>
> is this correct?
ping
> pavel
> commit c5d65f
Richard Heck wrote:
> Pavel Sanda wrote:
>> i see. as there was no feedback i suppose this module will stay locally on
>> my box, so no additional tweaks needed...
>>
>>
> Actually, I meant to be endorsing it.
is this correct?
pavel
commit c5d65f6eb648e7c109530a18128ddc718503facf
Author: Pavel
Pavel Sanda wrote:
i see. as there was no feedback i suppose this module will stay locally on
my box, so no additional tweaks needed...
Actually, I meant to be endorsing it.
rh
pavel
Richard Heck wrote:
>> OK then it is for configure.py, not for lyx.exe. Still, maybe this ought
>> to be parsed by lyx.exe too so why putting that into comments? Richard?
>>
> I'm confused about what you two are discussing.
i understand your confusion - there are more "comments" discussed :)
we w
Abdelrazak Younes wrote:
Pavel Sanda wrote:
Abdelrazak Younes wrote:
The layout format is a LyX internal format, I don't understand why
LyX should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configur
Pavel Sanda wrote:
Abdelrazak Younes wrote:
The layout format is a LyX internal format, I don't understand why LyX
should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configure.py to work.
OK the
Abdelrazak Younes wrote:
> The layout format is a LyX internal format, I don't understand why LyX
> should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configure.py to work.
pavel
Pavel Sanda wrote:
Abdelrazak Younes wrote:
If this is something that will be parsed by LyX, it should not be in
comments.
yes it should :)
Could you please develop?
The layout format is a LyX internal format, I don't understand why LyX
should parse the comments.
Abdel.
Abdelrazak Younes wrote:
> If this is something that will be parsed by LyX, it should not be in
> comments.
yes it should :)
pavel
Pavel Sanda wrote:
hi,
what about adding this into trunk?
If this is something that will be parsed by LyX, it should not be in
comments.
Abdel.
hi,
what about adding this into trunk?
pavel
#\DeclareLyXModule[comment.sty]{Print Comments}
#DescriptionBegin
#Typeset comment notes in LyX. When used with notes-mutate lfun,
#it can be used even for normal LyX notes.
#DescriptionEnd
Format 11
AddToPreamble
\usepackage{comment}
\
On Monday 02 July 2007 12:02:32 Abdelrazak Younes wrote:
>
> OK then.
+1
> Abdel.
--
José Abílio
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I think it would be less confusing to have one test per controller and
so integrate the kernel().isBufferReadonly() call to
canApplyToReadOnly().
I don't think so. These two conditions might be used independent from each
other.
OK then.
Ab
Abdelrazak Younes wrote:
> I think it would be less confusing to have one test per controller and
> so integrate the kernel().isBufferReadonly() call to
> canApplyToReadOnly().
I don't think so. These two conditions might be used independent from each
other.
Jürgen
Jürgen Spitzmüller wrote:
http://bugzilla.lyx.org/show_bug.cgi?id=3909
http://bugzilla.lyx.org/show_bug.cgi?id=3943
Printing and view-source of read-only files (such as the documentation of an
installed LyX) is disallowed, since we block the passing of params and
viewing restrictively for
http://bugzilla.lyx.org/show_bug.cgi?id=3909
http://bugzilla.lyx.org/show_bug.cgi?id=3943
Printing and view-source of read-only files (such as the documentation of an
installed LyX) is disallowed, since we block the passing of params and
viewing restrictively for read-only buffers (if kernel
José Matos wrote:
On Tuesday 05 June 2007 16:30:07 Richard Heck wrote:
OK to commit?
Richard
OK.
Done
--
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==
On Tuesday 05 June 2007 16:30:07 Richard Heck wrote:
> OK to commit?
>
> Richard
OK.
--
José Abílio
This patch fixes a bug with non-spooled printing, namely, that the
printer named in the print dialog was ignored.
OK to commit?
Richard
--
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu
Hi,
please find attached a file where I listed all icons from ../images[/math]
that are printed with a black background or not printed at all. If there is a
need I could make them all printable.
--
Viele Grüße,
Hartmut
Hungerhilfe: http://www.thehungersite.com
Kampagne gegen den Ausverkauf de
Hi.. I wrote up a short document on how one can configure the metafont modes
to generate darker fonts for printed output... this is useful when printing
documents written in certain fonts (especially CM) to low resolution
printers where the output may be a little too light.. I'd promised to
This is the result from the following thread:
http://marc.theaimsgroup.com/?l=lyx-users&m=103654394122771&w=2
in the users's list about how to print notes, and what their purpose it
etc. To get a quick idea of what this is about, see
http://marc.theaimsgroup.com/?l=lyx-users&m=10366599
Angus Leeming wrote:
On Tuesday 22 October 2002 11:55 am, Rob Lahaye wrote:
Well, then we would totally miss the point of my patch.
I made the non-xforms changes ONLY to support better GUI
Xforms dialogs.
Bear with me and send the new files too.
OK! You've got my full support !
Here you g
On Tuesday 22 October 2002 11:55 am, Rob Lahaye wrote:
> Well, then we would totally miss the point of my patch.
> I made the non-xforms changes ONLY to support better GUI
> Xforms dialogs.
Bear with me and send the new files too.
Angus
Angus Leeming wrote:
On Tuesday 22 October 2002 9:58 am, Rob Lahaye wrote:
Be aware that this is a huge patch though:
Why don't we have a look at this in small chunks. Can you split
out the non-xforms changes and post them here, since they are a
small part of the whole. If they don't affec
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars might well break Rob's work if he continues committing
| large stylistic changes.
I'd say that the stylistic changes are small... but all over.
| I tend to agree with Allan, but I'll let Lars exercise his authority.
well... I tend to agree with
On Tuesday 22 October 2002 9:58 am, Rob Lahaye wrote:
> Be aware that this is a huge patch though:
Why don't we have a look at this in small chunks. Can you split
out the non-xforms changes and post them here, since they are a
small part of the whole. If they don't affect Qt, then they shouldn'
Allan Rae wrote:
>
> How broken will things get if we put Rob's patch in before 1.3.0?
> Maybe my memory is fuzzy but isn't it only cleanup and working on
> MVCing Document?
No, it's not that. But many other goodies Xforms/GUI related. See below.
> If it's going to break Qt in a big way then
On Tue, Oct 22, 2002 at 09:37:15AM +0100, Angus Leeming wrote:
> Lars might well break Rob's work if he continues committing
> large stylistic changes.
Yes, I am a bit worried by this as well. I do not want to lose Rob's patch
in exchange for the removal of a few trailing spaces on the end of a l
On Tuesday 22 October 2002 8:48 am, Allan Rae wrote:
> On 19 Oct 2002, Lars Gullik Bjønnes wrote:
> > Rob Lahaye <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > | Will include all that in my big patch to GUI for 1.4.0cvs,
> > | when it's ready.
> >
> > I am also doing this change as part of the qtclean
On 19 Oct 2002, Lars Gullik Bjønnes wrote:
> Rob Lahaye <[EMAIL PROTECTED]> writes:
[...]
> | Will include all that in my big patch to GUI for 1.4.0cvs, when it's ready.
>
> I am also doing this change as part of the qtclean-2 patch, so you
> will have a couple of conflicts to resolve, sorry about
Rob Lahaye <[EMAIL PROTECTED]> writes:
| > No, but it could be put in some src/frontend file. LyXView perhaps.
| > ... actually now since the LyXView has been moved into the frontends
| > the whole setMinibuffer function should be removed and the users of it
| > should just use LyXView::message di
Lars Gullik Bjønnes wrote:
Rob Lahaye <[EMAIL PROTECTED]> writes:
| // [--skip head of file here--]
| namespace Liason {
|
| void setMinibuffer(LyXView * lv, string const & msg)
| {
| lyx::Assert(lv);
| lv->message(msg);
| }
|
| } // namespace Liason
|
|
| This should not go into the contro
ds/controllers/ControlSearch.C
| frontends/controllers/ControlThesaurus.C
|
| which makes me believe that setMinibuffer() has nothing to do with
| printing,
correct
--
Lgb
ers/ControlThesaurus.C
which makes me believe that setMinibuffer() has nothing to do with printing,
but I'm not sure.
Regards,
Rob.
On Wed, 9 Jan 2002, Jose Abilio Oliveira Matos wrote:
> On Wednesday 09 January 2002 09:10, Allan Rae wrote:
> >> My `info dvips` does not mention the equals sign. It's from
> > tetex-1.0.7. I imagine Garst is also in the same boat.
> >
> > dvips -v
> > This is dvips(k) 5.86 Copyright 1999 Radi
On 9 Jan 2002, Jean-Marc Lasgouttes wrote:
> > "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
>
> Allan> My `info dvips` does not mention the equals sign. It's from
> Allan> tetex-1.0.7. I imagine Garst is also in the same boat.
>
> Hmmm...
>
> lapinot: dvips -v
> This is dvips(k) 5.86e Cop
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> My `info dvips` does not mention the equals sign. It's from
Allan> tetex-1.0.7. I imagine Garst is also in the same boat.
Hmmm...
lapinot: dvips -v
This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com)
lapin
On 9 Jan 2002, Jean-Marc Lasgouttes wrote:
> > "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
>
> Allan> I'm open to suggestions on how to handle this. The numbers you
> Allan> enter are fed to dvips (or whatever print command you have
> Allan> set). So after inspecting the `info dvips` I'd
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> I'm open to suggestions on how to handle this. The numbers you
Allan> enter are fed to dvips (or whatever print command you have
Allan> set). So after inspecting the `info dvips` I'd say: you're
Allan> screwed.
Why? The info page says
;re screwed.
> Yup :)
> > I can't see a solution amongst the options there. The "-p NUM" flag
> > looked hopeful but it starts printing from the first page numbered
> > NUM. And the "-pp FIRST-LAST" flag is described as equivalent to "-p
> &g
solution amongst the options there. The "-p NUM" flag
looked hopeful but it starts printing from the first page numbered
NUM. And the "-pp FIRST-LAST" flag is described as equivalent to "-p
FIRST -l LAST".
Although it may be possible to do some trickery with a combi
Juergen Spitzmueller wrote:
> Or do I miss something?
Obviously I do :-(
I does make of course a difference for the printer.
Juergen
Mark van Rossum wrote:
> You want to print a regular envelope, so you define a small paper
> size (9.5 x 4.25 inches in the US) and define it to be landscape.
>
> Unfortunately, this does not work.
> The landscape option does not work for custom paper sizes.
Indeed. But IMHO this is a limitation
On Fri, Oct 26, 2001 at 10:31:37AM -0400, Richard Harris wrote:
> When I print from inside LyX I see a series of commands in the status line.
> I would like to print LyX documents in batch mode from the command line.
> Is this possible?
Not directly.
> And if so, what would the commands be?
lyx
I have a developer question:
When I print from inside LyX I see a series of commands in the status line.
I would like to print LyX documents in batch mode from the command line.
Is this possible? And if so, what would the commands be?
Thanks
--
Richard Harris
Editor, Words on a Wire
http:/
On Mon, Sep 24, 2001 at 04:02:38PM -0400, [EMAIL PROTECTED] wrote:
> herbert held,
>
>
> > On Mon, 24 Sep 2001 [EMAIL PROTECTED] wrote:
>
> > > herbert harumphed,
> > > > "Richard E. Hawkins" wrote:
>
> > > Thanks, but this gives the error, File `time.sty' not found.
>
> > package time availa
this is a quick line in the preamble? Hack level is fine; i
> > > need to keep printing my math as I work on it.
>
> > in preamble:
> > \usepackage{time}
> > \newcommand\myTime{\now}
> > \lhead{\today - \myTime}
>
> > with layout->document->pagest
"Richard E. Hawkins" wrote:
>
> Okay, softball time :)
>
> I'd like a footer or header to print the print time & date on each page.
> I assume this is a quick line in the preamble? Hack level is fine; i
> need to keep printing my math as I work
On Thursday 17 May 2001 22:55, Richard E. Hawkins wrote:
> I updated my source this afternoon.
[snip...]
> The biggy, though, is that it crashes on print. Running in gdb,
>
> I get (before any dialog)
>
> Program received signal SIGSEGV, Segmentation fault.
> PrinterParams::~PrinterParams (t
I updated my source this afternoon.
Are mulit-line equations supposed to default to two columns now? I
notice the new edit-> math entries, but they don't make much sense.
Also, I can't insert labels in equations, although I think I saw
traffic on this.
The biggy, though, is that it crashes
Good Afternoon,
I just spent the morning compiling the new version of LyX after
making a CVS checkout. While running it I then tried to print and it
"cored".
Moe info: I compiled with gcc, I run solaris 2.7. The 1.16 version
compiled and printed w/no problem.
[2:24pm] 55 [~/t4]:hibernate% u
I don't know why I never noticed this before, and it's far from
earth-shattering, but I just noticed today that the print
dialog is different from almost anything else I've ever used.
Particularly, The initial cursor placement tends be in the number
of pages, with the first and second tab taking
Today's cvs. Not sure how long the problem has been there.
I get lots of error boxen. Details on request.
Garst
On Tue, Jan 23, 2001 at 06:06:22AM -0800, Gary Ray (Seattle) wrote:
> The other problem was that the print button did not function. I even
> wiped out
> share/lyx and started over, but no luck on the print button.
> Any ideas?
Do you have a print menu-item under the file->export menu-item ?
Does
There are two problems I discovered when building 1.1.6. One is that during
make install, many of the new files in share/lyx were not copied, so I was left
with a new binary and old 1.1.5fix2 files. This I fixed manually.
The other problem was that the print button did not function. I eve
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> In FormPreferences->Output->Printer, the "adapt output" checkbox
John> seems unclear. There are four cases here :
[...]
John> So in summary it looks like we should only pass a value to lpr
John> if there is some printer name entered by
In FormPreferences->Output->Printer, the "adapt output"
checkbox seems unclear. There are four cases here :
1) the user has entered a printer name, and
$PRINTER has a value. The user value should always override
$PRINTER by passing it to lpr.
2) the user has entered a pr
Allan Rae wrote:
>
> On Mon, 25 Sep 2000, Garst R. Reese wrote:
>
> > Allan, what kind of dictionary do Australians use? (no, that is not an
> > ethnic joke :)
>
> Usually a British English dictionary. The Evil Empire's installation
> offers a choice of country of Australia but from I'm told i
On Mon, 25 Sep 2000, Garst R. Reese wrote:
> Allan, what kind of dictionary do Australians use? (no, that is not an
> ethnic joke :)
Usually a British English dictionary. The Evil Empire's installation
offers a choice of country of Australia but from I'm told it just uses the
British English di
To get it to work I had to modify babel.sty and english.ldf.diff in
/usr/local/teTeX/share/texmf/tex/generic/babel
The diffs are attached, but there is probably a better solution to this
problem.
Allan, what kind of dictionary do Australians use? (no, that is not an
ethnic joke :)
Garst
--- babel
The last page of my document was a blank page with a red blank and page
separator above that paragraph. The reason I need this is because I was
printing 2 sided, odd pages first in normal order, then even pages in
reverse order.
LyX or gs ignored the blank page, which put the wrong pages on the
On Wed, Sep 15, 1999 at 04:56:15PM +0100, Ben Cazzolato wrote:
> I can suppress this manually by printing to a file then sending it to the
> printer using the option -h, ie lpr -h file.ps
>
> Is it possible to modify my lyxrc to incorporate the printer flag?
You should be able to
> I'm trying to suppress the annoying banner page that follows my file whenever I
> print dirrectly from Lyx to a HP4m-PS printer.
>
> I can suppress this manually by printing to a file then sending it to the
> printer using the option -h, ie lpr -h file.ps
> Is i
Hi
I'm trying to suppress the annoying banner page that follows my file whenever I
print dirrectly from Lyx to a HP4m-PS printer.
I can suppress this manually by printing to a file then sending it to the
printer using the option -h, ie lpr -h file.ps
Is it possible to modify my lyx
Hello,
How I can get lyx printing ? When I try I got a message "errors while
proceding" (it's seems to be during the conversion to a ps file) . I
can't print even the help documents though printing works fine on my
system. (Mandrake 6.0 on AMD 350).
Thanks for your help.
On Thu, 19 Aug 1999, Allan Rae wrote:
> On Thu, 19 Aug 1999, Juergen Vigna wrote:
>
> > If you select Default I think this is the LaTeX default paper-size
> > and you shouldn't define ANY papersize!!! And I think this is what
> > happens.
I noticed something yesterday that I thought was wierd a
On Thu, 19 Aug 1999, Duncan Simpson wrote:
>
> Actually there is another problem that the patches so far do not fix:
> view ps will crop it to whatever it thinks the paper size actually is
> anyway and this is a gs feature :-) This got me and my print
> queue---gs thought US letter and depidated
Allan Rae wrote:
>
> I've attached my patch to fix the custom page size printing problems.
> I've tested this myself and pretty confident it'll work properly. It's
> against the latest cvs but should apply okay to 1.0.4pre4. So Garst can
> you try this an
On 19-Aug-99 Duncan Simpson wrote:
>
> Actually there is another problem that the patches so far do not fix: view ps
> will crop it to whatever it thinks the paper size actually is anyway and this
> is a gs feature :-) This got me and my print queue---gs thought US letter and
> depidated my A
Actually there is another problem that the patches so far do not fix: view ps
will crop it to whatever it thinks the paper size actually is anyway and this
is a gs feature :-) This got me and my print queue---gs thought US letter and
depidated my A4 documents badly. The fix is to add -sPAPERSI
1 - 100 of 156 matches
Mail list logo
