From: Renzo Been <swangdoodles@gmail.com>
To: emacs-orgmode@gnu.org, dandavison7@gmail.com, nicolas.girard@nerim.net
Subject: Re: org-icons package
Date: Thu, 18 Aug 2011 22:13:45 +0200 [thread overview]
Message-ID: <CALYR0wZHxzynAeSPdJSEMyeO=mGuKz=S=LoC=-O-VMzhG=F4Gg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3966 bytes --]
Hi Dan, Nicolas and list,
In my previous mail I wrote about using (and upgrading it for use with the
latest version of org-mode) Nicolas Girard's org-icons package, see:
http://news.gmane.org/find-root.php?group=gmane.emacs.orgmode&article=44834
I've tried to contact Nicolas Girard (via e-mail and a google search). But I
have not heard back from him as yet.
When I checked the github for org-icons again I discovered that there was a
second branch by Dan Davison.
https://github.com/ngirard/org-icons/tree/dan
Dan,
Do you know how I can get in contact with Nicolas? Or do you have access to
the github for org-icons, so that it's code can be updated to work with the
latest version of org-mode? Did you and Nicolas ever think about including
org-icons into org-mode?
As for me, I'm happily using org-icons with org-mode 7.7, I've attached a new
and updated patch file that works on the latest org.el
Copy the patch "org-icons.patch" to the directory where you keep your "org.el"
cd to that directory
And then apply the patch like this:
patch -b org.el org-icons.patch
Of-course, if neither of you has the time to work on org-icons... I could make
a fork of the git repo, and make the changes myself. However, I do not have
much elisp knowledge...
Ciao,
Renzo
On 25 July 2011 12:12, Renzo Been <swangdoodles@gmail.com> wrote:
> Bastien <bzg <at> altern.org> writes:
>> Hi Philipp,
>> Philipp Haselwarter <philipp.haselwarter <at> gmx.de> writes:
>> > Is there any particular reason for it to be hardcoded? Apart from the
>> > fact that /well it just is this way right now/ I mean.
>> Nothing carved in stone, but here are the two reasons I see:
>> - we don't want users to use arbitrary regexp to match headlines as they
>> are very likely to shoot themselves in the foot (Harven's example of
>> using "-" instead of "*" is a good example of that.)
>> - Given this, I am not able to imagine a good way of limiting the number
>> of allowed characters.
>> > That'd be useful information for anyone interested in changing it.
>> I'd interested in any solution to the problems above.
>> > Then
>> > you can still just tell them to write a patch if they care that much
>> > ('cause even in org-mode-land patches don't write themselves just yet)
>> :)
>> > [I just had the most awesome idea for a feature request].
>> Please share!
>> > If it's "just" about inheriting from a variable in some 300 places it
>> > could at least be discussed.
>> Yep -- if you have the energy to go through the code and see where it is
>> hardcoded while it should not, please do.
>> Thanks,
> Hi,
> I was just thinking... If you want to change the "look" of the
> org-headlines. Does one really need to change the code?
> I have been using Nicolas Girard's org-icons package for quite a while. And
> that makes org-buffers look pretty nice. You can even customise the icons, to
> make it look the way you want.
> However, some things about the org-icons package... It seems to be a little
> outdated. Are there many org-moders out there still using it? Were there
> ever any plans to include it in the org-distribution? Right now it needs to be
> installed by hand, because the patch to org.el is outdated... Also, I need to
> load it two times in my .emacs before the icons work...
> Ciao,
> Renzo
> The org-icons can be found here:
> Download from Nicolas Girard's github
> http://github.com/ngirard/org-icons
> On the Worg site I could only find screenshots, no other information...
> http://orgmode.org/worg/org-screenshots.html
> The list-message announcement for org-icons
> http://news.gmane.org/find-root.php?message_id=%3c87zl2962um.fsf%40stats.ox.ac.uk%3e
> And some list-messages discussing including the org-icons-patch into org-mode
> http://news.gmane.org/find-root.php?message_id=%3c87zlbx3kvf.fsf%40kassiopeya.MSHEIMNETZ%3e
[-- Attachment #2: ngirard-org-icons-renzo.tar.gz --]
[-- Type: application/x-gzip, Size: 429520 bytes --]
next reply other threads:[~2011-08-18 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 20:13 Renzo Been [this message]
2011-08-18 20:48 ` org-icons package Dan Davison
2011-08-19 21:50 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2011-08-19 21:39 Renzo Been
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='CALYR0wZHxzynAeSPdJSEMyeO=mGuKz=S=LoC=-O-VMzhG=F4Gg@mail.gmail.com' \
--to=swangdoodles@gmail.com \
--cc=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicolas.girard@nerim.net \
/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).