emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: project-explorer package forcing new frame... better solution than mine?
Date: Mon, 17 Nov 2014 10:52:25 +0100	[thread overview]
Message-ID: <86lhnagnmu.fsf@example.com> (raw)
In-Reply-To: 877fyxi00k.fsf@uw.edu

Brady Trainor wrote:
> Hi, I'm trying the project-explorer package. It uses a persistent
> window for a browsing tree.
>
> This causes a new frame when using any of org-export-dispatch,
> org-agenda-view menu, ibuffer-other-window, and org-insert-link. (My
> C-c C-e, C-c C-a, C-x C-b, C-c C-l.)
>
> I've made a solution for the export-dispatch (since I use
> project-explorer and org-export quite a bit for my Jekyll site). The
> solution is as follows:
>
> #+BEGIN_SRC emacs-lisp
> (add-hook 'project-explorer-mode-hook
>           (lambda ()
>             (make-variable-frame-local 'org-export-dispatch-use-expert-ui)
>             (modify-frame-parameters nil '((org-export-dispatch-use-expert-ui . t)))))
> #+END_SRC
>
> The author of project-explorer asserts that this may be a problem with
> Org-mode or Emacs.
>
> Since this also appears with ibuffer-other-window, is this necessarily
> worth mentioning to the Emacs newsgroup?
>
> Any ideas on a simpler solution than mine? 

I don't use such an explorer, but did you look at speedbar (or sr-speedbar)?

There is as well a very nice one in the CEDET collection, but I dunno if
it can be used in isolation.

Best regards,
  Seb

-- 
Sebastien Vauban

      reply	other threads:[~2014-11-17  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15  4:22 project-explorer package forcing new frame... better solution than mine? Brady Trainor
2014-11-17  9:52 ` Sebastien Vauban [this message]

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=86lhnagnmu.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).