From: Daniel Clemente <firstname.lastname@example.org> To: Carsten Dominik <email@example.com> Cc: org-mode mailing list <firstname.lastname@example.org> Subject: Re: Too much text is interpreted as a code fragment Date: Sat, 07 Feb 2009 11:32:22 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <FBFEE41C-0D24-49C0-85C6-1932B0F0B44A@uva.nl> (Carsten Dominik's message of "Sat, 7 Feb 2009 08:28:26 +0100") Carsten Dominik <firstname.lastname@example.org> writes: > stuff you do not want interpreted should be protected as > an example, or with ": " at the beginning of the line. > If you do want this interpreted as HTML, put it into a BEGIN_HTML block or so. > However, I think that the => of the clock should always be protected. I also see it strange that it only happens if a double quote is present: ---------------------- ***** the bug happens with this one CLOCK: [2009-02-06 dv 09:39]--[2009-02-06 dv 10:12] => 0:33 a="b ***** doesn't happen (no highlight) CLOCK: [2009-02-06 dv 09:39]--[2009-02-06 dv 10:12] => 0:33 a=b ---------------------- It's not so strange to write =" in an entry -- Daniel
next prev parent reply other threads:[~2009-02-07 10:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-07 0:23 Daniel Clemente 2009-02-07 1:59 ` Sebastian Rose 2009-02-07 10:27 ` Daniel Clemente 2009-02-07 7:28 ` Carsten Dominik 2009-02-07 10:32 ` Daniel Clemente [this message] 2009-02-07 11:34 ` Carsten Dominik
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Too much text is interpreted as a code fragment' \ /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
Code repositories for project(s) associated with this 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).