From: despen@verizon.net (Dan.Espen)
To: help-gnu-emacs@gnu.org
Subject: Re: I'm looking for a project management system for Emacs
Date: Sun, 30 Mar 2014 10:18:40 -0400 [thread overview]
Message-ID: <ictxafydkv.fsf@home.home> (raw)
In-Reply-To: mailman.18551.1396166787.10748.help-gnu-emacs@gnu.org
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> Dnia 2014-03-30, o godz. 00:29:53
> despen@verizon.net (Dan.Espen) napisał(a):
>
>> > Well, I thought I was clear enough...
>>
>> Yeah, I guess I only read it all once.
>>
>> >> The Makefile has to have the file list anyway.
>> >
>> > Assuming that you use make, which is not necessarily true. And
>> > even if I do use make, then see point 2 above: I probably wouldn't
>> > include the org file (which might contain TODOs etc. for many
>> > projects) anywhere in the Makefile (at least I see no reason to do
>> > so, other than to put it there so it contains a full list...)
>> >
>> > I guess you are thinking of "a project" in terms of "a software
>> > project". This might be true or not, in my case (assuming a usual
>>
>> Nope, big Gnumake fan here.
>> Any directory/project I do work in is going to have Makefile(s).
>
> Well, then I deduce that you are not a heavy LaTeX user. (Am I right,
> dear Watson? ;) ) The problem is that the make model (using
> timestamps) is a bit too simplistic for LaTeX: due to the way
> references (& friends) work, the .aux file basically depends on
> itself, but only if it contains a line saying
Right. Latex is for printing isn't it?
I do a lot of documentation writing.
But HTML/CSS (and Makefiles) are my weapon of choice.
I have rules for content generation (like a TOC), uploading, thumbnail
creation, packaging...
--
Dan Espen
next prev parent reply other threads:[~2014-03-30 14:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18471.1396076481.10748.help-gnu-emacs@gnu.org>
2014-03-29 17:11 ` I'm looking for a project management system for Emacs Dan.Espen
2014-03-29 18:03 ` Marcin Borkowski
[not found] ` <mailman.18509.1396116232.10748.help-gnu-emacs@gnu.org>
2014-03-30 4:29 ` Dan.Espen
2014-03-30 8:06 ` Marcin Borkowski
[not found] ` <mailman.18551.1396166787.10748.help-gnu-emacs@gnu.org>
2014-03-30 14:18 ` Dan.Espen [this message]
2014-03-30 19:14 ` Marcin Borkowski
2014-03-31 17:34 ` hubert
[not found] ` <mailman.18567.1396206860.10748.help-gnu-emacs@gnu.org>
2014-03-30 20:30 ` Dan.Espen
2014-03-30 21:02 ` Marcin Borkowski
2014-03-29 6:56 Marcin Borkowski
2014-03-29 9:35 ` Thorsten Jolitz
2014-03-29 18:12 ` Marcin Borkowski
2014-03-29 15:22 ` Drew Adams
2014-03-29 18:21 ` Marcin Borkowski
2014-03-29 18:24 ` Jai Dayal
2014-03-29 19:02 ` Drew Adams
2014-04-02 12:31 ` lee
2014-04-10 12:12 ` Jude DaShiell
2014-04-03 1:38 ` Robert Thorpe
2014-04-03 13:14 ` Alex Bennée
2014-03-29 20:45 ` Renato
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ictxafydkv.fsf@home.home \
--to=despen@verizon.net \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).