From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: [ANN] Org-babel integrated into Org-mode Date: Sat, 26 Jun 2010 21:42:08 +0200 Message-ID: <77BB8502-8CE1-4284-AED4-E751378B3A21@gmail.com> References: <87wrtp78rg.fsf@gmail.com> <87aaqkvqdi.fsf@mundaneum.com> <87iq585rb9.fsf@gmail.com> <87mxuji0n9.fsf@gmail.com> <87zkyiuqpt.fsf@gmail.com> <87fx09bx9h.fsf@gmail.com> <87k4plvjr0.fsf@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=56723 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OSbGZ-0004vo-Sy for emacs-orgmode@gnu.org; Sat, 26 Jun 2010 15:42:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OSbGY-0002j8-EQ for emacs-orgmode@gnu.org; Sat, 26 Jun 2010 15:42:15 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:57713) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OSbGY-0002ir-AU for emacs-orgmode@gnu.org; Sat, 26 Jun 2010 15:42:14 -0400 Received: by wyb39 with SMTP id 39so2470875wyb.0 for ; Sat, 26 Jun 2010 12:42:12 -0700 (PDT) In-Reply-To: <87k4plvjr0.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?UTF-8?Q?=C5=A0t=C4=9Bp=C3=A1n_N=C4=9Bmec?= Cc: emacs-orgmode@gnu.org, Rainer M Krug On Jun 26, 2010, at 6:30 PM, =C5=A0t=C4=9Bp=C3=A1n N=C4=9Bmec wrote: > "Eric Schulte" writes: > >> =C5=A0t=C4=9Bp=C3=A1n N=C4=9Bmec writes: >> >> [...] >>> >>> How come some of your rewrites above still use the `org-babel-' =20 >>> prefix? >>> (As a side note, I don't see what Emacs guidelines suggest `ob-' =20 >>> is more >>> appropriate than `org-babel-', and I would personally prefer to =20 >>> retain >>> the latter -- it's much more descriptive.) >>> >>> =C5=A0t=C4=9Bp=C3=A1n >>> >> >> Hi =C5=A0t=C4=9Bp=C3=A1n, >> >> The guidelines I mentioned (I believe) specify that all file names =20= >> for >> emacs-lisp files which are part of Emacs must be unique in the =20 >> first 6 >> or so characters. This is why all "(require 'ob-*)" lines (which =20 >> must >> correspond to file names) now use ob-* instead of org-babel-*. =20 >> Since I >> (like you) prefer the org-babel-* prefixes, those have been =20 >> retained for >> all function and variable names. > > I see. Hm... could you provide some source for that? The only > restriction on file names I can recall is this section from Appendix D > of the Emacs Lisp Reference Manual: > > * Please keep the names of your Emacs Lisp source files to 13 > characters or less. This way, if the files are compiled, the > compiled files' names will be 14 characters or less, which is > short enough to fit on all kinds of Unix systems. This is a restriction from the compiler. However, Emacs wants to be installable on many systems, including MS-=20 DOS, which has only 8+3 character file names. Therefore, Emacs =20 requires that the names are unique in the first 8 letters - they may =20 be longer than 8, but they must be unique when shortened. I cannot find the reference now, but I did explicitly ask a short =20 while ago and got this confirmed by Stefan Monnier. > > Is that perhaps what you meant? In any case, I see that the > recommendation I quote above would make the file renaming necessary, > too. > > (Also, I believe you actually did mention renaming *functions*, which > created my confusion in the first place -- cf. the commit message of > e0e4d76094f26 for example.) > >> Hope this explains it, I'm certainly open to other naming =20 >> suggestions. > > It would make a lot of sense to at least still begin the file names =20= > with > `org' IMHO, if at all possible. This will not solve the problem, I fear. - Carsten=