From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: recurring events, alternative to shift modifier, tag positions, smart [ ], and org-publish questions
Date: Sun, 10 Dec 2006 11:38:37 +0100 [thread overview]
Message-ID: <87ejr8yr0y.fsf@tallis.ilo.ucl.ac.uk> (raw)
In-Reply-To: <b2e202b30612081411h771ca285ma7a8362c1225ea48@mail.gmail.com> (Scott Jaderholm's message of "Fri\, 8 Dec 2006 15\:11\:16 -0700")
"Scott Jaderholm" <jaderholm@gmail.com> writes:
> I've had fun customizing the faces a little and this is what I came up
> with http://jaderholm.com/screens/org-colors.jpg
Nice!
> 2. I use org-mode over ssh and since shift doesn't work along with
> other modifiers many of the keystrokes do not work. Has anyone come
> up with alternate keystrokes not involving shift that they could
> share?
Have a look at this:
,----[ (info "(org)TTY keys") ]
| Org-mode uses a number of keys that are not accessible on a tty.
| This applies to most special keys like cursor keys, <TAB> and <RET>,
| when these are combined with modifier keys like <Meta> and/or
| <Shift>.
`----
> 4. Has anyone written a smart function for smart adding [ ] to
> lines, kind of like C-c C-t does with TODO? Ideally it would be
> smart enough to put it after a - if there were one.
- [ ] sklgj
>
> * Org-publish questions
>
> 5. I'm using org-export and I have been unable to link to an image and
> have it show up as an image in the exported html.
> [[Http://foo.com/bar.jpg]] shows up as a link and @<img
> src="http://foo.com/bar.jpg" /> shows up with the markup as text and
> the url as a link.
>
> 6. I've had problems with lists (- items) not ending correctly and the
> next line, even if separated with a blank line, is considered part of
> the list. Do I have to explicitly end the list or has anyone seen this
> problem? The closest I can get to reproducing it at this moment is
> that if I have:
>
> Text: - 1 - 2
>
> More text
>
> The "text:" is in a <p> but the "more text" is not in a <p>.
>
> 7. Is there a way to change how the page title is exported so that it
> will use a span instead of an h1?
>
> Thank you very much, Scott
>
> _______________________________________________ Emacs-orgmode mailing
> list Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
Bastien
next prev parent reply other threads:[~2006-12-10 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jaderholm@gmail.com>
2006-12-08 22:11 ` recurring events, alternative to shift modifier, tag positions, smart [ ], and org-publish questions Scott Jaderholm
2006-12-09 10:29 ` Pete Phillips
2006-12-09 18:20 ` Scott Jaderholm
2006-12-09 18:31 ` Russell Adams
2006-12-09 10:44 ` Pete Phillips
[not found] ` <3d6808890612090505hf8921a0g557d73ec0df57c49@mail.gmail.com>
2006-12-09 13:05 ` Tim O'Callaghan
2006-12-09 13:22 ` J. David Boyd
2006-12-10 10:38 ` Bastien [this message]
2006-12-10 10:41 ` Bastien
2006-12-12 8:11 ` 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 \
--in-reply-to=87ejr8yr0y.fsf@tallis.ilo.ucl.ac.uk \
--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).