emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Skip Collins <skip.collins@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: new export dispatcher window
Date: Fri, 15 Feb 2013 13:30:21 -0500	[thread overview]
Message-ID: <CABUh-745_ZUabsLXDeV7ChrMjAbG5=NaSLBgUUsoE44EYRAXgw@mail.gmail.com> (raw)

The new export dispatcher confused me when it displayed an incomplete
list of backend options. At first I thought my configuration must not
be loading LaTeX and HTML properly. Then I discovered that the *Org
Export Dispatcher* window does not behave well when the frame is too
small. I am using the GUI version of GNU Emacs for Mac OS X. I
verified that the same problem exists when running in a terminal.

I have the LaTeX, Beamer, HTML, and iCal backends enabled. I open a
new terminal (80x24) and type
emacs test.org
When I invoke the dispatcher with C-c C-e, a new dispatch window opens
at the bottom. The terminal screen looks like this (I truncated a
couple of lines to avoid line wrapping in this email):

---start screen---
File Edit Options Tools Buffers Services Help



-UUU:----F1  test.org       All L1     (Org) ---------------------
    [L] As Latin1 buffer          [l] As Latin1 file
    [U] As UTF-8 buffer           [u] As UTF-8 file

[P] Publish
    [f] Current file              [p] Current project
    [x] Choose project            [a] All projects

[&] Export stack
[q] Exit








-UUU:**--F1  *Org Export Dispatcher*   Bot L33    (Fundamental) --
Export command:
---end screen---

The dispatcher does not properly display all available options and
does not use all available space. I cannot get it to scroll. If I make
my terminal window larger (80x40) and do the same thing, I get better
results:

---start screen---
File Edit Options Tools Buffers Services Help



-UUU:----F1  test.org       All L1     (Org) ---------------------
Options
    [C-b] Body only:    Off       [C-v] Visible only:     Off
    [C-s] Export scope: Buffer    [C-f] Force publishing: Off
    [C-a] Async export: Off

[c] Export to iCalendar
    [f] Current file              [a] All agenda files
    [c] Combine all agenda files

[h] Export to HTML
    [H] As HTML buffer            [h] As HTML file
    [o] As HTML file and open

[l] Export to LaTeX
    [L] As LaTeX buffer           [l] As LaTeX file
    [p] As PDF file               [o] As PDF file and open
    [B] As LaTeX buffer (Beamer)  [b] As LaTeX file (Beamer)
    [P] As PDF file (Beamer)      [O] As PDF file and open (Beamer)

[o] Export to ODT
    [o] As ODT file               [O] As ODT file and open

[t] Export to Plain Text
    [A] As ASCII buffer           [a] As ASCII file
    [L] As Latin1 buffer          [l] As Latin1 file
    [U] As UTF-8 buffer           [u] As UTF-8 file

[P] Publish
    [f] Current file              [p] Current project
    [x] Choose project            [a] All projects

[&] Export stack
[q] Exit
-UUU:**--F1  *Org Export Dispatcher*   All L33    (Fundamental) --
Export command:
--- end screen---

             reply	other threads:[~2013-02-15 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 18:30 Skip Collins [this message]
2013-02-15 19:47 ` new export dispatcher window Nicolas Goaziou
2013-02-16  4:38   ` Skip Collins
2013-02-16  7:09     ` Nicolas Goaziou
2013-02-16 14:46       ` Skip Collins
2013-02-16 14:53         ` Nicolas Goaziou

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='CABUh-745_ZUabsLXDeV7ChrMjAbG5=NaSLBgUUsoE44EYRAXgw@mail.gmail.com' \
    --to=skip.collins@gmail.com \
    --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).