From: Ivan Vanyushkin <vanav@vanav.com.ua>
To: Ryan Thompson <rct@thompsonclan.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: S-Tab strange behavour
Date: Tue, 02 Feb 2010 22:38:31 +0200 [thread overview]
Message-ID: <4B688D47.5060208@vanav.com.ua> (raw)
In-Reply-To: <2a4ba2fd1002021140m43ed89ecof918578f08889c30@mail.gmail.com>
There is org-startup-folded that controls startup state, so org-mode
should know it.
Also S-Tab forgets state even in the middle of document. Key presses to
reproduce:
1) S-Tab - OVERVIEW
2) S-Tab - CONTENTS
3) C-G (or any other)
4) S-Tab - OVERVIEW (expected: SHOW ALL)
or
1) S-Tab - OVERVIEW
3) C-G (or any other)
4) S-Tab - OVERVIEW (nothing changed! expected: CONTENTS)
Is it by design? Why?
On 02.02.2010 21:40, Ryan Thompson wrote:
> I don't think it is possible in general to know the startup state of a
> file. Files with a #+STARTUP line may be an execption.
>
> On Tue, Feb 2, 2010 at 11:28 AM, Ivan Vanyushkin<vanav@vanav.com.ua> wrote:
>> Hello.
>>
>> On initial file opening, S-<TAB> cycles through
>> 1) OVERVIEW -> 2) CONTENTS -> 3) SHOW ALL
>> not depending on current state of document.
>>
>> So, if (as default) document is in OVERVIEW state, first press
>> _does nothing_ (switch to OVERVIEW again). Expected: CONTENTS.
>>
>> If document initially "#+STARTUP: content", then first press switches it
>> back to OVERVIEW. Expected: SHOW ALL.
>>
>> So, S-Tab (and maybe Tab) doesn't use context state when start cycling.
>>
>> Is it correct and why?
>>
>> org-version 6.21 and 6.34c
>> Emacs 23.1.1
>>
>> Thank you for your answer!
>>
>>
>> --
>> Ivan Vanyushkin - Vanav.
next prev parent reply other threads:[~2010-02-02 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 19:28 S-Tab strange behavour Ivan Vanyushkin
2010-02-02 19:40 ` Ryan Thompson
2010-02-02 20:38 ` Ivan Vanyushkin [this message]
2010-02-02 21:25 ` Ryan Thompson
2010-02-03 10:13 ` Ivan Vanyushkin
2010-02-03 10:30 ` 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=4B688D47.5060208@vanav.com.ua \
--to=vanav@vanav.com.ua \
--cc=emacs-orgmode@gnu.org \
--cc=rct@thompsonclan.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).