headers
Bram Moolenaar | 1 Sep 2003 20:00
Picon

Re: Question about :execute {pass}


Scott Witscher wrote:

> I have a question about the behavior of the :execute function.  When I
> use the {pass} option the execute command does not set variables that
> are specified on the :execute command line.  This does work without
> the {pass} option.  Is this the intended behavior or is this a bug?
> 
> When I run aap on the example below I get the following output.
> 
> > aap
> -DFOO
> -DBAR
> 
> > aap bad
> Aap: Error in recipe "/tmp/aaptest/main.aap" line 2: NameError: name 'vary' is not defined

I have now fixed this problem.  The arguments of ":execute" ended up in
the wrong dictionary.  Aap 1.023 will be available later today.

--

-- 
ZOOT:  I'm afraid our life must seem very dull and quiet compared to yours.
       We are but eightscore young blondes, all between sixteen and
       nineteen-and-a-half, cut off in this castle, with no one to protect us.
       Oooh.  It is a lonely life ... bathing ...  dressing ... undressing ...
       making exciting underwear....
                 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
(Continue reading)

Permalink | Reply | 751 comments |
headers
Adriaan de Groot | 1 Sep 2003 22:49
Picon
Picon

One more stab at an XML docbook tools tutorial

 <at> if os.name == "FreeBSD":
    Installing the XML docbook tools from ports is by far the easiest thing
    to do. I have the following ports installed for XML docbook:
	docbook-xml-4.2_1   XML version of the DocBook DTD
	docbook-xsl-1.61.3_1 XSL DocBook stylesheets
	libxml2-2.5.10      Xml parser library for GNOME
	libxslt-1.0.32      The XSLT C library for GNOME
	sdocbook-xml-4.1.2.5_1 "Simplified" DocBook XML DTD
	xmlcatmgr-0.2_1     SGML/XML catalog manager
    You can portinstall(1) them in the order libxml2, libxslt, docbook-xml,
    docbook-xsl. The remaining two get pulled in automatically. Once this is 
    done, you should have an executable /usr/local/bin/xsltproc and
    directories /usr/local/share/xml and xsl.
 <at> elsif os.name == "SuSE":
    (see also the "else:" branch below)
    You can make do with the following 4 rpms for xml and 
    xsl processing: libxml2-2.5.8-8, libxml2-devel-2.5.8-8,
    libxslt-1.0.31-7, libxslt-devel-1.0.31-7. They might be standard
    with some SuSE releases. They can certainly be fetched from
    SuSE's site. The docbook DTD and stylesheets are also available
    as rpm's, I found them on rpmfind.net as:
ftp://fr.rpmfind.net/linux/SuSE-Linux/i386/8.2/suse/src/docbook_4-4.2-214.src.rpm
ftp://fr.rpmfind.net/linux/SuSE-Linux/i386/8.2/suse/src/docbook-xsl-stylesheets-1.60.1-22.src.rpm
    also, it turns out that "Docbook: The Definitive Guide" is
    available as an rpm by itself, at
ftp://fr.rpmfind.net/linux/SuSE-Linux/i386/8.2/suse/noarch/docbook-tdg-2.0.6-75.noarch.rpm
    I imagine that after installing all that, you'll have a working xsltproc
    and the stylesheets installed somewhere - probably /usr/share, but you can
    use 'find / -name chunk.xsl' to find out where exactly.
 <at> else:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bram Moolenaar | 2 Sep 2003 10:34
Picon

Re: One more stab at an XML docbook tools tutorial


Adriaan de Groot wrote:

>  <at> if os.name == "FreeBSD":
>     Installing the XML docbook tools from ports is by far the easiest thing
[...]

I'm glad you figured out how to do all this.

> xsltproc if it is not in your path in the recipe. It also adds a workaround 
> if you do not have "links" installed, which is a HTML-to-text converter tool.

I just discovered that a more recent version of "links" no longer
supports the "-dump" argument, thus can't be used to convert HTML to
plain text.  I have added a fallback to use Lynx instead:

     <at> try:
	:sys links -dump exec.html >exec.txt
     <at> except:
	:sys lynx -dump -nolist exec.html >exec.txt

Exception handling is great, isn't it?  I still prefer the recipe to
fail with an error when "exec.txt" can't be produced.

> The new recipe does not generate pdf. I know generating pdf is
> possible and straightforward, but I haven't talked to the right people
> yet as to how to do it. 

I do need to produce the PDF file.  Thus I'll postpone switching to XML
until you manage to add this.  I think this needs to be done with "jade"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 4 Sep 2003 21:16
Picon

news: Installing Aap made easier


Installing Aap made easier

The download page has been updated. Now there is a step-by-step
explanation for installing Aap and Agide on Unix, MS-Windows and Mac OS
X. The procedure has been simplified, especially for Agide. Most work
can be done automatically with aap --install agide.

See: http://www.a-a-p.org/download.html

--

-- 
DEAD PERSON:  I'm getting better!
CUSTOMER:     No, you're not -- you'll be stone dead in a moment.
MORTICIAN:    Oh, I can't take him like that -- it's against regulations.
                                  The Quest for the Holy Grail (Monty Python)

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 16 Sep 2003 21:21
Picon

news: list of packages on web site


List of packages added

A page has been added to list the packages that can currently be
installed with:

	aap  --install  package-name
	
The list has been growing steadily and it is not obvious which package
is available on what system. You can find the list here:
http://www.a-a-p.org/packages.html.

--

-- 
Some of the well know MS-Windows errors:
	EMEMORY		Memory error caused by..., eh...
	ELICENSE	Your license has expired, give us more money!
	EMOUSE		Mouse moved, reinstall Windows
	EILLEGAL	Illegal error, you are not allowed to see this
	EVIRUS		Undetectable virus found

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
(Continue reading)

Permalink | Reply | 0 comments |
headers
grubert | 17 Sep 2003 07:52
Picon
Gravatar

Re: news: list of packages on web site

On Tue, 16 Sep 2003, Bram Moolenaar wrote:

>
> List of packages added
>
> A page has been added to list the packages that can currently be
> installed with:
>
> 	aap  --install  package-name
>
> The list has been growing steadily and it is not obvious which package
shouldnt this mean "now" _____________________/^^^

> is available on what system. You can find the list here:
> http://www.a-a-p.org/packages.html.

--

-- 
 BINGO: Green Flag
 --- Engelbert Gruber -------+
  SSG Fintl,Gruber,Lassnig  /
  A6170 Zirl   Innweg 5b   /
  Tel. ++43-5238-93535 ---+

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 17 Sep 2003 22:20
Picon

Re: news: list of packages on web site


Engelbert Gruber wrote:

> On Tue, 16 Sep 2003, Bram Moolenaar wrote:
> > List of packages added
> >
> > A page has been added to list the packages that can currently be
> > installed with:
> >
> > 	aap  --install  package-name
> >
> > The list has been growing steadily and it is not obvious which package
> shouldnt this mean "now" _____________________/^^^
> 
> > is available on what system. You can find the list here:
> > http://www.a-a-p.org/packages.html.

I certainly didn't want to say something this confusing.  Let's make it:
"it mentions which package is available on what system".

--

-- 
Never under any circumstances take a sleeping pill
and a laxative on the same night.

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

-------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 22 Sep 2003 14:42
Picon

Zimbu award reminder


You still have a chance to earn a Zimbu award.  Be quick though, your
contribution to Aap must be submitted by September 30!

        444 euro award for the best contribution to the A-A-P project
        222 euro award for the most useful patch for Aap or Agide
        111 euro award for the brightest idea for the A-A-P project

Read more about the Zimbu award here:

	http://www.a-a-p.org/zimbu_award.html

--

-- 
hundred-and-one symptoms of being an internet addict:
2. You kiss your girlfriend's home page.

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Permalink | Reply | 0 comments |
headers
Adriaan de Groot | 24 Sep 2003 10:27
Picon
Picon

some $BDIR/target query

1) Why does AAP build targets in the recipe dir, not in $BDIR? In particular, 
this recipe:

:program foo : bar.c

builds $BDIR/bar.o and then foo. Why not $BDIR/foo? Suppose I organize my 
sources into directories:

:program foo : foo/bar.c

now AAP will try to build $BDIR/foo/bar.o, and then foo -- which is a 
directory, and will fail.

--

-- 
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot@...>
     Key fingerprint = 934E 31AA 80A7 723F 54F9  50ED 76AC EE01 FEA2 A3FE

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Permalink | Reply | 1 comment |
headers
Bram Moolenaar | 25 Sep 2003 11:03
Picon

Re: some $BDIR/target query


Adriaan de Groot wrote:

> 1) Why does AAP build targets in the recipe dir, not in $BDIR? In particular, 
> this recipe:
> 
> :program foo : bar.c
> 
> builds $BDIR/bar.o and then foo. Why not $BDIR/foo? Suppose I organize my 
> sources into directories:
> 
> :program foo : foo/bar.c
> 
> now AAP will try to build $BDIR/foo/bar.o, and then foo -- which is a 
> directory, and will fail.

The idea behind this is that intermediate results can be put anywhere,
you don't need to know where.  Since $BDIR differs from system to system
there is no fixed location where they are stored.

The resulting program is the final result, thus it must be in the place
where the user expects it.  You could argue that $BDIR/foo is that
place, but after typing "aap" to build your program, a user doesn't know
if it ended up in build-FreeBSD4_8_RELEASE or build-OtherSystem_8, thus
you can't execute the program without looking carefully where it is.

If you have a different situation it's very easy to specify the
directory where you want your executable to be stored.  You could use:

	:program $BDIR/foo : foo/bar.c
(Continue reading)

Permalink | Reply | 0 comments |

Gmane