From: Andrew Hyatt <ahyatt@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Tassilo Horn <tassilo@member.fsf.org>, emacs-orgmode@gnu.org
Subject: Re: Re: Release 6.30
Date: Wed, 2 Sep 2009 07:28:08 -0400 [thread overview]
Message-ID: <c8389b600909020428n3ad156fcm6125c8137e6db099@mail.gmail.com> (raw)
In-Reply-To: <F21CA5C7-1D17-4C77-B69F-148F7900EB45@gmail.com>
Yep, that was my confusion. Thanks!
On Wed, Sep 2, 2009 at 5:30 AM, Carsten
Dominik<carsten.dominik@gmail.com> wrote:
>
> On Sep 2, 2009, at 10:11 AM, Tassilo Horn wrote:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> it is this commit:
>>>
>>> bbc27c011ab5d44d37dca662d1a393d429dbe4b3
>>
>> That commit is in, but grepping for separate-frame in all *.el files
>> gives no result and the docs don't mention it, too.
>>
>> ,----[ C-h v org-agenda-window-setup RET ]
>> | org-agenda-window-setup is a variable defined in `org-agenda.el'.
>> | Its value is reorganize-frame
>> |
>> | Documentation:
>> | How the agenda buffer should be displayed.
>> | Possible values for this option are:
>> |
>> | current-window Show agenda in the current window, keeping all other
>> windows.
>> | other-frame Use `switch-to-buffer-other-frame' to display agenda.
>> | other-window Use `switch-to-buffer-other-window' to display agenda.
>> | reorganize-frame Show only two windows on the current frame, the
>> current
>> | window and the agenda.
>> | See also the variable `org-agenda-restore-windows-after-quit'.
>> `----
>>
>> Looking at "git show bbc27c011ab5d44d37dca662d1a393d429dbe4b3" it seems
>> to me, that there's no new value, but that other-frame now uses a
>> dedicated window.
>
> Yes, this seems to have been a typo in the release notes. You need to use
> the value `other-frame'.
>
> - Carsten
>
>>
>> Bye,
>> Tassilo
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
next prev parent reply other threads:[~2009-09-02 11:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 4:20 Release 6.30 Carsten Dominik
2009-09-01 11:19 ` Sebastian Rose
2009-09-01 13:55 ` Bernt Hansen
2009-09-01 13:56 ` [PATCH] Fix typo in org-submit-bug-report mail text Bernt Hansen
2009-09-01 19:00 ` Release 6.30 Andrew Hyatt
2009-09-02 7:01 ` Carsten Dominik
2009-09-02 8:11 ` Tassilo Horn
2009-09-02 9:30 ` Carsten Dominik
2009-09-02 11:28 ` Andrew Hyatt [this message]
2009-09-04 10:03 ` Rainer Stengele
2009-09-05 5:55 ` Carsten Dominik
2009-09-05 14:08 ` Rainer Stengele
2009-09-06 11:41 ` Carsten Dominik
2009-09-06 17:21 ` Rainer Stengele
2009-09-06 18:58 ` Rainer Stengele
2009-09-06 20:53 ` 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=c8389b600909020428n3ad156fcm6125c8137e6db099@mail.gmail.com \
--to=ahyatt@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tassilo@member.fsf.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).