feature request: more control over opening links

feature request: more control over opening links

[Samuel Wales]

Summary: C-u C-u to force opening in an external application.

Detail:

My ideal settings for opening links would by default have
org-open-at-point and org-open-at-point-global open
everything in emacs except for anything that makes little
sense to open in emacs, such as PDF (whether http:// or a
local filename).  This would include html pages on the web,
which I want opened in emacs-w3m by default.

Then, for cases where that does not work, C-u would open in
emacs always.  C-u C-u would open in external always.
"External" here means the OS default (e.g. the "open"
command in OS X).

That way, when I know that I want something different, I can
force it.  (An alternate design is to reverse the sense of
what org-file-apps says.  But then you have to think about
what the default is and decide whether to reverse it.  This
seems an unnecessary cognitive burden.)

This seems not to be possible now.  If I set most things to
open in Emacs, I think that there is no way to open it in
the OS default.  Is that correct?

Re: feature request: more control over opening links

[Ross Patterson]

"Samuel Wales" <samologist@gmail.com> writes:

> Summary: C-u C-u to force opening in an external application.
>
> Detail:
>
> My ideal settings for opening links would by default have
> org-open-at-point and org-open-at-point-global open
> everything in emacs except for anything that makes little
> sense to open in emacs, such as PDF (whether http:// or a
> local filename).  This would include html pages on the web,
> which I want opened in emacs-w3m by default.
>
> Then, for cases where that does not work, C-u would open in
> emacs always.  C-u C-u would open in external always.
> "External" here means the OS default (e.g. the "open"
> command in OS X).
>
> That way, when I know that I want something different, I can
> force it.  (An alternate design is to reverse the sense of
> what org-file-apps says.  But then you have to think about
> what the default is and decide whether to reverse it.  This
> seems an unnecessary cognitive burden.)
>
> This seems not to be possible now.  If I set most things to
> open in Emacs, I think that there is no way to open it in
> the OS default.  Is that correct?

+1 - I like this idea a lot.

Ross

Re: feature request: more control over opening links

[Carsten Dominik]

Hi Samuel

   (you never sign your mails, so do not know if you prefer "Sam"...)

this is a reasonable request, and I have just implemented it.

Note, however, that it only applies to "file:" links, as
detailed in my previous message.

- Carsten

On Nov 4, 2008, at 8:43 PM, Samuel Wales wrote:

> Summary: C-u C-u to force opening in an external application.
>
> Detail:
>
> My ideal settings for opening links would by default have
> org-open-at-point and org-open-at-point-global open
> everything in emacs except for anything that makes little
> sense to open in emacs, such as PDF (whether http:// or a
> local filename).  This would include html pages on the web,
> which I want opened in emacs-w3m by default.
>
> Then, for cases where that does not work, C-u would open in
> emacs always.  C-u C-u would open in external always.
> "External" here means the OS default (e.g. the "open"
> command in OS X).
>
> That way, when I know that I want something different, I can
> force it.  (An alternate design is to reverse the sense of
> what org-file-apps says.  But then you have to think about
> what the default is and decide whether to reverse it.  This
> seems an unnecessary cognitive burden.)
>
> This seems not to be possible now.  If I set most things to
> open in Emacs, I think that there is no way to open it in
> the OS default.  Is that correct?
>
>
> _______________________________________________
> 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

Re: feature request: more control over opening links

[Samuel Wales]

On Wed, Nov 5, 2008 at 02:50, Carsten Dominik <dominik@science.uva.nl> wrote:
> this is a reasonable request, and I have just implemented it.

Thanks!

> Note, however, that it only applies to "file:" links, as
> detailed in my previous message.

Yes, I now realize that the same work will have to be done to
browse-url.  Somehow I had forgotten about that.