|
From: | Ivan Vanyushkin |
Subject: | [Orgmode] Re: S-Tab strange behavour |
Date: | Wed, 03 Feb 2010 12:13:41 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 |
On 02.02.2010 23:25, Ryan Thompson wrote:
If the previous command was anything else, then Org Mode has no idea whether the buffer or its visibility has changed since the last-executed S-Tab, since it cannot know which other commands will affect buffer visibility and which will not.
I think, only Org changes visibility, so it can track current state.
On Tue, Feb 2, 2010 at 12:38 PM, Ivan Vanyushkin<address@hidden> wrote: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<address@hidden> 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.
[Prev in Thread] | Current Thread | [Next in Thread] |