emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 4.68
Date: Fri, 16 Mar 2007 19:39:52 +0100	[thread overview]
Message-ID: <874polyqvb.fsf@bzg.ath.cx> (raw)
In-Reply-To: <b21e6a719e5c39840831e1ecd328e4a4@science.uva.nl> (Carsten Dominik's message of "Fri\, 16 Mar 2007 18\:08\:33 +0100")

Carsten Dominik <dominik@science.uva.nl> writes:

> I have forwarded this mail to David O'Toole, to find out if he still
> feels responsible for changes in org-publish.  Lets wait if he responds.

Okay. I'll see if i'm able to go through org-publish and track this down.

>>   What about using C-c <return> to insert a plain |---- line *and* go
>> down
>>   to a cell ?  Currently, it's still bounded to org-insert-heading.
>
> Do you mean down to a cell in the current column, or down to the first
> cell in the row below the newly inserted hline?

Down to the first cell in the row below the newly inserted hline.

> You have two options:
>
> 1.  Make a table using the table.el package.  

I'll try this one in cases where i don't want to use the narrowing
workaround (which is usually fine).

> I guess this is not very well though-out, and maybe it would be good
> to simply export the text before the first heading.

Definitely.  +1 vote! 

>> * *[[link]]* are not boldified when exported to HTML.
>
> No it does not.  Should it?  What is the purpose of making some links
> bold? Are you thinking about internal or external links?  Would CSS maybe
> be a better place to address formatting of links?

I was using links with the #+LINK system, looking for words in wikipedia
like this : [[wikipedia:Word][Word]].  And then highlighting some words in
the text, some of them beeing *also* links.  But you're right, no need to
fontified links more than necessary.

> I cannot reproduce this.  Could you make an example file and show the
> ics entry you get?  Thanks!

Er.  I cannot reproduce this anymore.  BTW, the main problem is that links
in headings are exported as it: [[...][...]].  I think we should just keep
the descriptive part of links in iCal.

Thanks,

-- 
Bastien

  reply	other threads:[~2007-03-16 18:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13  4:31 Org-mode version 4.68 Carsten Dominik
2007-03-16 11:11 ` Bastien
2007-03-16 17:08   ` Carsten Dominik
2007-03-16 18:39     ` Bastien [this message]
2007-03-18  7:00       ` Carsten Dominik
2007-03-17 11:38     ` David O'Toole
2007-03-31 21:58       ` T. V. Raman
2007-05-21  6:36         ` Carsten Dominik
2007-03-19 14:21     ` Alex Fu
2007-03-20 12:14       ` Carsten Dominik
2007-03-21  6:59   ` Carsten Dominik
2007-03-21  8:58     ` Bastien
2007-03-22  8:25 ` Leo

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=874polyqvb.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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).