emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Renzo Been <swangdoodles@gmail.com>
To: Dan Davison <dandavison7@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-icons package
Date: Fri, 19 Aug 2011 23:39:45 +0200	[thread overview]
Message-ID: <CAK_Tu5koQkmp+anrSXP81aHvkSSS2_-0nPLsKOioaJi77MmO=g@mail.gmail.com> (raw)

Oké Dan,

Understood. That sounds right; to move all the code into the
org-icons.el file. That way the patch is no longer needed, and
org-icons can live in the contrib dir (together with a directory for
the images).

I think its best if I make a fork of your repo. That gives me some
space for working on the code. Once I have made some progress (I won't
be very fast...), I will send you a Pull request.

The changes that you have made until now, are found here:
https://github.com/dandavison/org-devel/tree/org-icons/contrib/org-icons
Right?

Your right, org-icons is a nice way to change the looks of org
buffers. I'll go through the code first, to get an understanding of
what can be done.

Ciao,
Renzo

On 18 August 2011 22:48, Dan Davison <dandavison7@gmail.com> wrote:
> Hi Renzo,
> org-icons needs to be moved into contrib/, hooked in via a lightweight patch
> against org.el, instead of being implemented as a monolithic change to
> org.el. I made a start on that in this branch:
> https://github.com/dandavison/org-devel/tree/org-icons
> but I'm not sure that I got very far. Note that that is a branch in a clone
> of the org repo, as opposed to the org-icons repos which are standalone
> repos and do not contain org.
> I thought org-icons was interesting because it offers the possibility of
> allowing users to make arbitrary superficial changes to org aesthetics. For
> example, the #+begin_src...#+end_src boilerplate is rather heavy for some
> peoples' tastes. At one point I had it replacing that with a little (ruby,
> snake) for (ruby, python) code... But I think it also allows the possibility
> of overlaying with text. I'd be happy to give you push access to that repo,
> but, you may as well just fork it as I have no plans to work on it.
> I don't know how to contact Nicolas. I believe that he is on record as
> saying he did not plan to develop org-icons further.
> Good luck,
> Dan

             reply	other threads:[~2011-08-19 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 21:39 Renzo Been [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-18 20:13 org-icons package Renzo Been
2011-08-18 20:48 ` Dan Davison
2011-08-19 21:50   ` Bastien
2011-07-14 13:53 how to change the headline starter * harven
2011-07-14 15:47 ` Bastien
2011-07-14 19:28   ` Philipp Haselwarter
2011-07-15 10:56     ` Bastien
2011-07-25 10:12       ` org-icons package (was: how to change the headline starter *) Renzo Been
2011-07-27 15:50         ` org-icons package 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='CAK_Tu5koQkmp+anrSXP81aHvkSSS2_-0nPLsKOioaJi77MmO=g@mail.gmail.com' \
    --to=swangdoodles@gmail.com \
    --cc=dandavison7@gmail.com \
    --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).