emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Joost Helberg <joost-JFNXyGN8thM@public.gmane.org>
Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug: code blocks with multiple word names create single word result-blocks leading to collisions [8.2.10 (8.2.10-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20141013/)]
Date: Wed, 18 Feb 2015 14:59:32 +0100	[thread overview]
Message-ID: <86zj8bnwvv.fsf@example.com> (raw)
In-Reply-To: <87twyjiazq.fsf-JFNXyGN8thM@public.gmane.org> (Joost Helberg's message of "Wed, 18 Feb 2015 14:51:21 +0100")

Joost Helberg wrote:
> "Sebastien" == Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> writes:
>> Joost Helberg wrote:
>>> noweb-syntax allows blanks in names of code blocks.
>
>> Are you sure?  Where did you read that?
>
> It's in https://www.cs.tufts.edu/~nr/noweb/johnson-lj.pdf.

Well, that's the real noweb, not Org's partial implementation.

> In org-mode it works as specified; the noweb expansion of names with
> multiple words works fine.
>
>>> The result-blocks of these code blocks are named as well, but have
>>> everything behind the first word stripped. This leads to
>>> result-block collisions in case there are two code blocks starting
>>> with the same word.
>
>> Quite logic if, in fact, it just reads the first token... which is
>> what happens, IIUC.
>
> I expect it to read the full name, which may have more than one word.
>
>> Of course, you could expect to get an error or warning reported.
>
> In order to run snippets of code which are also in use as noweb-items,
> it's currently impossible to use names with multiple words where the
> first word collides with other names. My patch allows the use of code
> blocks with sentences as names hence enjoying the literate in literate
> programming a lot more.
>
> I fail to see a reason for the result-blocks to have only one-word
> names, it doesn't break anything if these carry the full name of the
> code block.

I understand you may desire that, and that it can be useful, but I'm not
sure whether this is so obvious to implement.

Nicolas will certainly give you more information on that.

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2015-02-18 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 12:54 Bug: code blocks with multiple word names create single word result-blocks leading to collisions [8.2.10 (8.2.10-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20141013/)] Joost Helberg
2015-02-18 13:06 ` Sebastien Vauban
2015-02-18 13:51   ` Joost Helberg
     [not found]     ` <87twyjiazq.fsf-JFNXyGN8thM@public.gmane.org>
2015-02-18 13:59       ` Sebastien Vauban [this message]
2015-02-18 14:05 ` Nicolas Goaziou

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=86zj8bnwvv.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    --cc=joost-JFNXyGN8thM@public.gmane.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).