From: "Thomas S. Dye" <tsd@tsdye.com>
To: Peter Davis <pfd@pfdstudio.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BeOrg
Date: Tue, 02 Jan 2018 14:30:56 -1000 [thread overview]
Message-ID: <m24lo3aim7.fsf@tsdye.com> (raw)
In-Reply-To: <1514931452.4092041.1222235240.37A13EBE@webmail.messagingengine.com>
Aloha all
Peter Davis writes:
> On Tue, Jan 2, 2018, at 3:43 PM, Nicolas Goaziou wrote:
>>
>> I think you are missing the point. Free software is primarily
>> about
>> source code (the four definitions).
> If we refuse to provide useful information just because it
> violates some
> purist idea of what is or is not acceptably unencumbered, then
> we’re
> just denying users potential helpful capabilities that may make
> the
> difference between using org-mode or abandoning it completely in
> favor
> of some commercial, cross-platform solution.
IIUC, the question is about where to provide this information, not
whether or not to provide it. OP asked about putting it in the
Org manual and Nicolas has pointed out that the manual is for
documenting Org software.
Perhaps Worg is a better place to provide information about BeOrg?
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2018-01-03 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 17:32 BeOrg Ilya Shlyakhter
2018-01-02 17:39 ` BeOrg Eric S Fraga
2018-01-02 17:52 ` BeOrg ilya shlyakhter
2018-01-02 19:20 ` BeOrg Nicolas Goaziou
2018-01-02 19:48 ` BeOrg Ilya Shlyakhter
2018-01-02 20:43 ` BeOrg Nicolas Goaziou
2018-01-02 22:17 ` BeOrg Peter Davis
2018-01-03 0:30 ` Thomas S. Dye [this message]
2018-01-03 2:06 ` BeOrg Ian Dunn
2018-01-03 2:43 ` BeOrg Ilya Shlyakhter
2018-01-03 5:00 ` BeOrg Scott Randby
2018-01-03 20:00 ` BeOrg Adonay Felipe Nogueira
2018-01-03 8:26 ` BeOrg Tim Cross
2018-01-03 19:58 ` BeOrg Adonay Felipe Nogueira
-- strict thread matches above, loose matches on Subject: below --
2018-01-05 2:08 BeOrg edgar
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=m24lo3aim7.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=pfd@pfdstudio.com \
/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).