From: Spike Spiegel <fsmlab@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Indentation problem
Date: Thu, 28 May 2009 01:05:28 +0800 [thread overview]
Message-ID: <ab777dfe0905271005y2c8d3ca9y94c236239b0eb5cf@mail.gmail.com> (raw)
In-Reply-To: <87skiqhcwk.fsf@gollum.intra.norang.ca>
On Wed, May 27, 2009 at 9:51 PM, Bernt Hansen <bernt@norang.ca> wrote:
> Is your TAB key bound to the correct function? (C-h k TAB) gives me
> - <tab> runs the command yas/expand
> in my regular setup and
> - <tab> runs the command org-cycle
> in my minimal emacs setup
>
> Both work the same for me.
I haven't figured out what yet, but cleaning out my settings and only
importing a few selected ones and re-checking out 6.27a made it work,
should have done that before sorry. On the other hand I'm not sure
what you mean with "regular setup" and "minimal emacs setup". With the
orgmode loaded c-h k <TAB> tells me org-cycle.
that said, if I copy paste something I still get the long lines
incorrectly indented. For example, given:
** TODO something to do
SCHEDULED: <2009-05-30 Sat>
[2009-05-27 Wed]
and then pasting stuff from the c-h k <TAB> I get:
** TODO something to do
SCHEDULED: <2009-05-30 Sat>
[2009-05-27 Wed]
This is the command invoked in Org-moe by the TAB key. It's main purpose
is outine visibility cycling, but it also invokes other actions
in special contexts.
(Note that positioning the cursor after Wed] then RET and then TAB
moved the cursor to the expected position)
thoughts?
--
"Behind every great man there's a great backpack" - B.
next prev parent reply other threads:[~2009-05-27 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 12:06 Indentation problem Spike Spiegel
2009-05-27 13:51 ` Bernt Hansen
2009-05-27 17:05 ` Spike Spiegel [this message]
2009-05-27 17:15 ` Bernt Hansen
-- strict thread matches above, loose matches on Subject: below --
2009-09-16 9:48 indentation problem Rainer Stengele
2009-09-18 13:10 ` 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=ab777dfe0905271005y2c8d3ca9y94c236239b0eb5cf@mail.gmail.com \
--to=fsmlab@gmail.com \
--cc=bernt@norang.ca \
--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).