Vladimir Zhbanov wrote:
One problem I noticed before is no way to reprint all .eps-files from
command line, that is from Makefile also.
ack. A way to recursively print all schematics in a hierarchy is missing in
the bag of features.
---)kaimartin(---
--
Kai-Martin Knaak
On Thu, Nov 25, 2010 at 11:50:36PM +0100, kai-martin knaak wrote:
Vladimir Zhbanov wrote:
It would be nice to have the same way to make EPS too. What if
you need to make LaTeX files with images
This is what I use the PDF output for :-)
Last I used latex rather than pdflatex must have
On Wed, Nov 24, 2010 at 03:42:31AM +0100, kai-martin knaak wrote:
John Doty wrote:
S2PS=gschem -p -o $@ -s print.scm $
Thanks!
I completely missed the existence of that simple scheme script. I
wasn't even aware of the possibility to do this kind of scripting.
You can call me stupid,
Vladimir Zhbanov wrote:
It would be nice to have the same way to make EPS too. What if
you need to make LaTeX files with images
This is what I use the PDF output for :-)
Last I used latex rather than pdflatex must have been about 2005...
which should have the same scale?
Good point. In
Peter Brett wrote:
What is the prupose of ~A in this line?
It's a Scheme format specifier. I think in this case I will invite
you to RTF Guile Manual, since it explains the operation of the
'format' function quite well. :-)
(Apologies for top-posting)
Postscript is passed to the standard input of the print command, which is run
using popen(). It uses the default shell 'sh' to run the command.
I think that the sort of behaviour you're looking for might be best achieved by
writing some sort of wrapper program that
Kai-Martin Knaak kn...@iqo.uni-hannover.de writes:
But if I try to access the produced pdf file with
lp -d PDF -t mosfet-node; mv $HOME/PDF/mosfet-node.pdf .
the second command seems to act on the state before the print command. If
there was no PDF file before, I get:
mv:
On Nov 23, 2010, at 6:20 AM, Kai-Martin Knaak wrote:
Still, I'd like to have a one touch PDF output. Or, even better, non-GUI
printing from a script.
The following Makefile rules do the job for me, using the print.scm distributed
with gEDA.
S2PS=gschem -p -o $@ -s print.scm $
John Doty wrote:
S2PS=gschem -p -o $@ -s print.scm $
Thanks!
I completely missed the existence of that simple scheme script. I
wasn't even aware of the possibility to do this kind of scripting.
You can call me stupid, now...
There is a similar image.scm one for PNG output, too :-)
Peter TB Brett wrote:
(define %file-print file-print)
(define (file-print)
(print-command (format #f lp -d PDF -t \~A\ (get-selected-filename)))
(gschem-use-rc-values)
(%file-print))
It is horrible and nasty, but it seems to work.
It does work!
How does it work? By
John Doty wrote:
What's the current schematic at gschem startup, when gschemrc
is executed?
The one given on the command line?
Anyway, for the purpose of the print command, the expression
should be evaluated when the print dialog is brought up, not
at the start of the session. The gschemrc
It does work!
How does it work? By replacing an internal gschem script?
Essentially, yes.
What is the prupose of ~A in this line?
It's a Scheme format specifier. I think in this case I will invite you to RTF
Guile Manual, since it explains the operation of the 'format' function quite
Currently, my print command in gschemrc is
(print-command lp -d PDF)
This prints a PDF of the current schematic via cups-pdf.
The PDF file appears in $HOME/PDF/ as
job_1296-untitled_document.pdf
I'd like to replace this with the name of the schematic. The lp command can
set
Paul Tan wrote:
(get-selected-filename) is a Gschem Scheme procedure which
returns the current page filename as string.
Unfortunately, my gschem segfaults right away, if gschemrc contains the
(get-selected-filename) procedure. It segfaults even if the line is
reduced to
(define name
On 11/19/2010 07:18 PM, kai-martin knaak wrote:
Paul Tan wrote:
(get-selected-filename) is a Gschem Scheme procedure which
returns the current page filename as string.
Unfortunately, my gschem segfaults right away, if gschemrc contains the
(get-selected-filename) procedure. It
Hi Kai-Martin Knaak,
Oh, I remember there is a bug in the gschem/src/g_funcs.c file.
You may want to change the get_selected_filename function
in g_funcs.c file, (around line number 299), as follows:
/*
= */
SCM
Hi Kai-Martin Knaak,
(depending on your email system, some lines in the
code below may be just a long single line. So I am
re-sending with the fix for this. Hope it
comes out ok now)
Oh, I remember there is a bug in the gschem/src/g_funcs.c file.
You may want to change the get_selected_filename
John Doty wrote:
Well, it shouldn't segfault, but I'm not surprised you can't
evaluate it in gschemrc before there is a selected file. What
did you expect to happen?
From the doxygen comment:
* This function gets the whole filename of the current schematic.
* Specifically, the
Paul Tan wrote:
Hope it helps.
I still get segfaults. My get_selected_filename procedure
looks like this now:
/---
SCM get_selected_filename(GSCHEM_TOPLEVEL *w_current)
{
gchar* s;
SCM return_value;
exit_if_null(w_current);
s =
On 11/19/2010 08:59 PM, kai-martin knaak wrote:
John Doty wrote:
Well, it shouldn't segfault, but I'm not surprised you can't
evaluate it in gschemrc before there is a selected file. What
did you expect to happen?
From the doxygen comment:
* This function gets the whole filename
On Friday 19 November 2010 12:22:05 Kai-Martin Knaak wrote:
I'd like to replace this with the name of the schematic. The lp command can
set the base name of the file with the option -t. But how would I teach
gschemrc to automatically fill in the file name of the current schematic?
Is there
21 matches
Mail list logo
