From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: Why not push?
Date: Sun, 15 Feb 2015 11:56:01 +0100 [thread overview]
Message-ID: <87egprwiim.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <87oaov3173.fsf@ericabrahamsen.net>
On 2015-02-15, at 11:42, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Hello,
>>
>> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>>
>>> I don't want to be nitpicking, but I'm just curious. I'm looking at the
>>> function `org-split-string'. It uses (two times) the following
>>> construction:
>>>
>>> (setq list (cons (something) list))
>>>
>>> Is there any particular reason for not using `push' there?
>>
>> No. Good luck with refactoring "org.el". ;)
>
> Shhh... if you don't say anything, he might go and do it!
;-)
Actually, not. (Though it might make a nice student project. And it
would be a good idea to do it.) But I haven't signed the FSF papers.
OTOH, I have a personal project where I devote some amount of time every
day to read someone else's code. I started with parts of simple.el, and
now the time has come for ox-latex (and its dependencies).
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-02-15 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 10:23 Why not push? Marcin Borkowski
2015-02-15 10:38 ` Nicolas Goaziou
2015-02-15 10:42 ` Eric Abrahamsen
2015-02-15 10:56 ` Marcin Borkowski [this message]
2015-02-15 12:26 ` Eric Abrahamsen
2015-02-15 22:31 ` Marcin Borkowski
2015-02-15 21:22 ` Yuri Niyazov
2015-02-15 21:31 ` Nicolas Goaziou
2015-02-15 21:40 ` Marcin Borkowski
2015-02-15 11:35 ` Rasmus
2015-02-15 22:33 ` Marcin Borkowski
2015-02-16 9:03 ` Sebastien Vauban
2015-08-05 0:00 ` Bastien Guerry
2015-08-05 6:21 ` Nicolas Goaziou
2015-08-05 7:07 ` Bastien Guerry
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=87egprwiim.fsf@wmi.amu.edu.pl \
--to=mbork@wmi.amu.edu.pl \
--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).