emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: BUG: coderef labels not stripped when tangling
Date: Thu, 24 Jan 2013 16:19:25 +0100	[thread overview]
Message-ID: <86vcamvcaq.fsf@somewhere.org> (raw)
In-Reply-To: 87sj5qu236.fsf@ironicdesign.com

Michael,

Michael Alan Dorman wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Or a feature, with the consequence that you should put those refs as comments
>> (with the appropriate syntax in your language).
>
> That is an excellent suggestion for resolving my immediate issue that
> had not occured to me at all.  It believe it does mean that the
> presentation of the code ends up with seemingly empty comments where the
> coderefs were, but that's a relatively minor thing.

Glad it helped!

>> But, yes, those comments stay as well in your tangled code, which you may not
>> like.
>
> It seems counter-intuitive to me that text that is regarded as
> meta-information when rendering for presentation is not treated
> similarly when tangling---a needless mismatch between the two processes.

I'll let Eric answer on this...

> But thanks for your workaround suggestion, I will definitely take
> advantage of it.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2013-01-24 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 13:05 BUG: coderef labels not stripped when tangling Michael Alan Dorman
2013-01-24  9:27 ` Sebastien Vauban
2013-01-24 13:45   ` Michael Alan Dorman
2013-01-24 15:19     ` Sebastien Vauban [this message]
2013-01-24 15:49     ` Bastien
2013-02-13 14:21 ` Bastien
2013-02-13 16:26   ` Michael Alan Dorman

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=86vcamvcaq.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@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).