emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Bastien <bzg@altern.org>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: Meaning of install
Date: Fri, 15 Mar 2013 13:06:55 -1000	[thread overview]
Message-ID: <m1mwu4fek0.fsf@tsdye.com> (raw)
In-Reply-To: <877gl8pd7l.fsf@bzg.ath.cx> (Bastien's message of "Fri, 15 Mar 2013 22:25:50 +0100")

Hi Bastien,

Bastien <bzg@altern.org> writes:

> Hi Thomas,
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>>> I would mention "make config" here for a sanity check of the created
>>> configuration.
>>
>> Good idea.  Done.
>
> Oh, I thought it was done in Org's org.texi manual but I understand
> this is done in orgmanual.git, right?

Yes, that's right. I'm bringing orgmanual.git up-to-date using the git
diff magic formula you sent me a week and a half ago and making some
edits as I go along. Changes to the installation section began as minor
edits, but grew as this thread went on.

> Could you make the change in org.texi too?

You have the persistence of a good maintainer. I haven't finished
editing the other installation sections, so I'm not in a position to
repeat my earlier reply to a similar query, which was to export
orgmanual! :)

I do hope it will be possible in the near future for me to take a larger
role in maintaining the Org manual. That is my goal. But for me to do
that the manual will need to be in Org, not texi. For purely personal
reasons that don't reflect at all on the Org community or the manual,
org.texi fills me with horror. If the orgmanual experiment fails then I
plan to beat a hasty retreat, lick my wounds, and work happily on other
interesting tasks at hand.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2013-03-15 23:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 16:04 Meaning of install Thomas S. Dye
2013-03-12 18:27 ` Yagnesh Raghava Yakkala
2013-03-12 19:02 ` Achim Gratz
2013-03-12 20:14   ` Thomas S. Dye
2013-03-12 20:29     ` Achim Gratz
2013-03-12 20:46     ` Nick Dokos
2013-03-13  4:05       ` Thomas S. Dye
2013-03-13  7:19         ` Achim Gratz
2013-03-13  8:00           ` Andreas Röhler
2013-03-13  8:43             ` Bastien
2013-03-13  9:11               ` Andreas Röhler
2013-03-13 11:56                 ` Bastien
2013-03-14 20:29                   ` Andreas Röhler
2013-03-13  8:00           ` Yagnesh Raghava Yakkala
2013-03-14 17:04           ` Thomas S. Dye
2013-03-14 17:24             ` Bastien
2013-03-14 19:03             ` Achim Gratz
2013-03-14 20:15               ` Thomas S. Dye
2013-03-15 21:25                 ` Bastien
2013-03-15 23:06                   ` Thomas S. Dye [this message]
2013-03-13  8:56 ` Bastien

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.orgmode.org/

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

  git send-email \
    --in-reply-to=m1mwu4fek0.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=Stromeko@nexgo.de \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).