Gnus development mailing list
 help / color / mirror / Atom feed
From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: Somebody working on make.bat /make-x.bat?
Date: Thu, 27 Feb 2003 21:06:58 +0100	[thread overview]
Message-ID: <uheap8p3x.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <b3lpug$qlm$1@ebel.dfakt.de>

frank paulsen <frank.paulsen@gmx.net> writes:

> Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
>
>> If there are more problems with the current solution, please let me
>> know.
>
> make.bat does not create lisp/gnus-load.el
>
> i added the following lines right after the compile phase, but i am
> not sure about the '.' for '$(srcdir)'.
>
> ,----[ make.bat ]--
> | %EMACSBATCH% -l ./dgnushack.el -f dgnushack-compile
> | %EMACSBATCH% -l ./dgnushack.el -f dgnushack-make-cus-load .
> | %EMACSBATCH% -l ./dgnushack.el -f dgnushack-make-auto-load .
> | %EMACSBATCH% -l ./dgnushack.el -f dgnushack-make-load
> `----
>
> EMACSBATCH contains '-batch -q', which seems to be redundant:
>
> ,----[ info Emacs ]--
> | `--batch'
> |      [...]
> |      `-batch' implies `-q' (do not load an init file).  It also causes
> |      Emacs to kill itself after all command options have been
> |      processed.  In addition, auto-saving is not done except in buffers
> |      for which it has been explicitly requested.
> `----

OK, I'll have a look at those, too.

-- 
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.



      reply	other threads:[~2003-02-27 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 22:08 Frank Schmitt
2003-02-27  7:52 ` Niklas Morberg
2003-02-27  8:48   ` Frank Schmitt
2003-02-27 19:46 ` frank paulsen
2003-02-27 20:06   ` Frank Schmitt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uheap8p3x.fsf@hschmi22.userfqdn.rz-online.de \
    --to=usereplyto@frank-schmitt.net \
    --cc=replies@Frank-Schmitt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).