From: Jambunathan K <kjambunathan@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [odt] htmlfontify + Support for src blockfontification
Date: Fri, 19 Aug 2011 13:52:46 +0530 [thread overview]
Message-ID: <81wre9yfmx.fsf@gmail.com> (raw)
In-Reply-To: <87ei0hrgcz.fsf@altern.org> (Bastien's message of "Fri, 19 Aug 2011 09:31:11 +0200")
Based on my experience I have received far more feedback/bug reports on
odt exporter since 7.6 release than when it was in my own git.
All three suggestions made here miss the whole point. They are
suggesting to hide a useful piece of work underneath githubs, repos etc.
- It is not a question of availability but it is a question of
availability at the right place where most users can find it without
even knowing it. (Did anyone know of org-icons package a few months
back?)
I am an artist, I need a stage and an audience. I am not a philosopher
who keeps his thoughts and work private for his own consumption.
- There also seem to be an unarticulated assumption that a transitional
software should be as perfect as a released software. It need not be
so.
Those who have been on the emacs-devel list would know that much of
the bidi development is already part of emacs-24 and the discussions
last few weeks have been more about tightening the screws and fixing
the user-experience component of it.
You would also similar parallels with buffer alist related
simplifications proposed by martin rudalics. If my understanding is
correct, they are genuine interest on the part of emacs developers to
steer the patch for overall good.
The rule of thumb is that don't hesitate to accept big pieces (provided
they are proven worthy - in a proof of concept sense of word).
Calling an enhanced htmlfontify.el a duplication is misstating of facts.
Again let me cite the example of htmlize. It is available publicly
(somewhere?). Why should it be part of contrib dir? I know at some point
it was a patched up version of the "original" htmlize.
If you are willing to engage in a discussion I can walk through it. If
the decision is unilateral I am afraid I cannot do much about it.
Btw, I have been sitting on an elpa patch since November of last
year. Everytime I submitted I had to spend atleast 1 hr+ to polish
it. Now it is totally forgotten.
Enough said ...
Jambunathan K.
--
next prev parent reply other threads:[~2011-08-19 8:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 20:36 [odt] htmlfontify + Support for src blockfontification Jambunathan K
2011-08-15 21:55 ` suvayu ali
2011-08-17 9:59 ` Bastien
2011-08-18 18:50 ` Jambunathan K
2011-08-18 18:57 ` Achim Gratz
2011-08-18 20:55 ` Jambunathan K
2011-08-18 23:10 ` suvayu ali
2011-08-19 7:31 ` Bastien
2011-08-19 8:22 ` Jambunathan K [this message]
2011-08-19 9:50 ` Bastien
2011-08-19 12:26 ` Jambunathan K
2011-08-19 12:49 ` Jambunathan K
2011-08-19 21:48 ` Bastien
2011-08-19 10:28 ` Bastien
2011-08-19 12:31 ` Jambunathan K
2011-08-19 20:20 ` Bastien
2011-08-19 10:31 ` Bastien
2011-08-19 12:13 ` Jambunathan K
2011-08-19 20:15 ` 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=81wre9yfmx.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--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).