From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Loris Bennett <loris.bennett@fu-berlin.de>, emacs-orgmode@gnu.org
Subject: Re: Structure info in minibuffer
Date: Thu, 02 Mar 2017 12:29:48 +0000 [thread overview]
Message-ID: <CAJ51EToEx3P4Seb=UzWvt_Lt4RwphJOdZtO+3O5+wBnWbC358g@mail.gmail.com> (raw)
In-Reply-To: <87inns3wed.fsf@fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Do you use org-ref? It did that for a short time. If so an update of
org-ref should make it go away.
On Thu, Mar 2, 2017 at 3:40 AM Loris Bennett <loris.bennett@fu-berlin.de>
wrote:
> Hi,
>
> I'm not exactly sure when this started happening, but I assume it came
> with the update to Org 9:
>
> In any org file, potentially lengthy information about (I'm guessing
> here) org objects is displayed in the minibuffer, e.g.:
>
> (headline (:raw-value Nutzer :begin 805 :end 3472 :pre-blank 0
> :contents-begin 814 :contents-end 3471 :level 1 :priority nil :tags nil
> :todo-keyword nil :todo-type nil :post-blank 1 :footnote-section-p nil
> :archivedp nil :commentedp nil :post-affiliated 805 :title Nutzer))
>
> In certain table cells, the minibuffer expands to 4 or 5 lines (of 180
> characters) in order to display the information.
>
> How can I turn this off?
>
> Cheers,
>
> Loris
>
> --
> This signature is currently under construction.
>
>
> --
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
[-- Attachment #2: Type: text/html, Size: 2169 bytes --]
next prev parent reply other threads:[~2017-03-02 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 8:39 Structure info in minibuffer Loris Bennett
2017-03-02 12:29 ` John Kitchin [this message]
2017-03-02 12:34 ` Loris Bennett
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='CAJ51EToEx3P4Seb=UzWvt_Lt4RwphJOdZtO+3O5+wBnWbC358g@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=loris.bennett@fu-berlin.de \
/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).