emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stephan Schmitt <drmabuse@cs.tu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: Re: [ANN] Org-babel integrated into Org-mode
Date: Sat, 26 Jun 2010 20:45:49 +0200	[thread overview]
Message-ID: <4C264ADD.1070201@cs.tu-berlin.de> (raw)
In-Reply-To: <877hllbt72.fsf@gmail.com>



Also sprach Eric Schulte:
> Štěpán Němec<stepnem@gmail.com>  writes:
>
>> "Eric Schulte"<schulte.eric@gmail.com>  writes:
>>
>>> Štěpán Němec<stepnem@gmail.com>  writes:
>>>
>>> [...]
>>>>
>>>> How come some of your rewrites above still use the `org-babel-' prefix?
>>>> (As a side note, I don't see what Emacs guidelines suggest `ob-' is more
>>>> appropriate than `org-babel-', and I would personally prefer to retain
>>>> the latter -- it's much more descriptive.)
>>>>
>>>>      Štěpán
>>>>
>>>
[...]
>> 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.
>>

Are there any unix systems running emacs 22 (iirc org-mode doesn't
support emacs 21 anymore) which have problems with long filenames?
We're living in the 21st century, aren't we?

[...]
>>
>> It would make a lot of sense to at least still begin the file names with
>> `org' IMHO, if at all possible.
>>
>
> hmm, the longest (non-language-specific) file name is already 12
> characters long,
>
> (length "ob-tangle.el") ;; =>  12
>
> which doesn't give us much room to play around with.  Looking at a
> couple of possible prefixes, and the related leftover characters for
> differentiating the *-tangle, *-comint, *-ref, etc... core babel files,
> yields the following
>
> | prefix   | remaining characters |
> |----------+----------------------|
> | ob-      |                    5 |
> | org-b-   |                    2 |
> | orgb-    |                    3 |
> | org-bbl- |                    0 |
> | bbl-     |                    4 |
> | babel-   |                    2 |
> #+TBLFM: $2='(sbe leftover (prefix $$1))
>
> #+source: leftover
> #+begin_src emacs-lisp :var prefix=""
>    (-
>     ;; length w/o .el
>     (- 13 (length ".el"))
>     ;; length of prefix
>     (length prefix))
> #+end_src
>
> Personally, none of the above seem to be particularly superior to the
> current naming scheme, given the fact that we need to fit multiple files
> behind this prefix.

I think you have to add 2 to each of the numbers above.
But the conclusion surely remains the same...

Greetings,
	Stephan

  reply	other threads:[~2010-06-26 18:46 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 21:09 [ANN] Org-babel integrated into Org-mode Eric Schulte
2010-06-23 23:23 ` Sebastian Rose
2010-06-23 23:41   ` Eric Schulte
2010-06-24  0:03 ` Bernt Hansen
2010-06-24  0:39   ` Eric Schulte
2010-06-24  5:12     ` Nathan Neff
2010-06-24  5:42       ` Eric Schulte
2010-06-24  7:31 ` Sébastien Vauban
2010-06-24 16:27   ` Eric Schulte
2010-06-25  8:28     ` Rainer M Krug
2010-06-25 15:37       ` Eric Schulte
2010-06-26  8:45         ` Štěpán Němec
2010-06-26 15:59           ` Eric Schulte
2010-06-26 16:30             ` Štěpán Němec
2010-06-26 17:27               ` Eric Schulte
2010-06-26 18:45                 ` Stephan Schmitt [this message]
2010-06-26 19:42               ` Carsten Dominik
2010-06-26 19:51                 ` Štěpán Němec
2010-06-28  7:55         ` Rainer M Krug
2010-06-28 11:53           ` Štěpán Němec
2010-06-28 12:16             ` Rainer M Krug
2010-06-28 12:54               ` Bernt Hansen
2010-06-28 13:18                 ` Rainer M Krug
2010-06-28 13:25                   ` Bernt Hansen
2010-06-28 13:36                     ` Rainer M Krug
2010-06-28 16:03           ` Eric Schulte
2010-06-29  7:11             ` Rainer M Krug
2010-06-28 11:32 ` Christopher Witte
2010-06-28 16:59   ` Eric Schulte
2010-07-02 15:50     ` Christopher Witte
2010-06-29 18:23 ` Matt Lundin
2010-06-29 19:08   ` Nick Dokos
2010-06-29 21:01     ` Matt Lundin
2010-06-29 21:27       ` Matthew Lundin
2010-06-29 22:12       ` Nick Dokos
2010-06-29 22:03   ` Eric Schulte
2010-06-29 23:09     ` Eric Schulte
2010-06-29 23:11       ` Eric Schulte
2010-06-30  2:21         ` Nick Dokos
2010-06-30  5:37           ` Eric Schulte
2010-06-30  5:40             ` Eric Schulte
2010-06-30 12:13     ` Matthew Lundin
2010-06-30  9:27   ` Carsten Dominik
2010-06-30  9:59     ` Scot Becker
2010-06-30 12:53     ` Matthew Lundin
2010-06-30 13:24       ` Carsten Dominik
2010-06-30 16:25     ` Eric Schulte
2010-06-30 17:01       ` Dan Davison
2010-06-30 17:17         ` Eric Schulte
2010-06-30 23:08           ` Stephan Schmitt
2010-07-01  0:20         ` Matthew Lundin
2010-07-01  6:27         ` Carsten Dominik
2010-07-01 16:11           ` Nick Dokos
2010-07-01 20:24             ` Sébastien Vauban
2010-07-01 22:14               ` Nick Dokos
2010-06-30 19:41       ` Eric Schulte
2010-07-01  7:20       ` Carsten Dominik
2010-07-01 14:55         ` Eric Schulte
2010-07-01 20:39           ` Eric Schulte
2010-07-01 22:13             ` Christian Moe
2010-07-02  4:22             ` Carsten Dominik
2010-07-02 18:52               ` Eric Schulte
2010-07-02  8:38           ` Carsten Dominik
2010-06-30 19:01   ` Eric Schulte
2010-06-30 20:47     ` Matthew Lundin

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=4C264ADD.1070201@cs.tu-berlin.de \
    --to=drmabuse@cs.tu-berlin.de \
    --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).