Re: at-mime and at-url

2011-12-06 Thread Offray Vladimir Luna Cárdenas

Hi,

On Sun Dec  4 07:21:59 2011, Josef wrote:

when the node body is empty, I can see currently no difference between
@url and @mime.

when the node body is *not* empty, double-clicking @url foo.pdf will
simply highlight the node head for editing,
while double-clicking @mime foo.pdf will open the pdf in the
associated viewer.

Since I use the node body to make annotations to a file, I prefer the
behavior of @mime.



You can still made annotations on the body using @url after a space and 
a line break. I do this and only use @url all the time.


Cheers,

Offray

--
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.



Re: at-mime and at-url

2011-12-06 Thread Terry Brown
On Sun, 4 Dec 2011 04:21:59 -0800 (PST)
Josef joe...@gmx.net wrote:

 when the node body is *not* empty, double-clicking @url foo.pdf will
 simply highlight the node head for editing,
 while double-clicking @mime foo.pdf will open the pdf in the
 associated viewer.

Do you have @setting

  @bool single_click_auto_edits_headline = True

?  If you set that to False I think double clicking an @url headline
will open the @url.  I have it set True, but dbl-click still opens the
@url as long as the node's not selected before the first click of the
double click.

Cheers -Terry

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.



Re: at-mime and at-url

2011-12-04 Thread Josef
when the node body is empty, I can see currently no difference between
@url and @mime.

when the node body is *not* empty, double-clicking @url foo.pdf will
simply highlight the node head for editing,
while double-clicking @mime foo.pdf will open the pdf in the
associated viewer.

Since I use the node body to make annotations to a file, I prefer the
behavior of @mime.


On Nov 29, 12:09 am, Dan White etihw...@gmail.com wrote:
 On Fri, Nov 18, 2011 at 5:26 AM, Josef joe...@gmx.net wrote:
  Although it seems @url can under some circumstances also open local
  files with the associated program, @mime certainly does a more
  consistent job, particularly with relative path names.

 Can you come up with an example where the behavior is different?  With
 the current core handling of UNLs, the changes should be minor.

 Dan

 --
 SDGwww.whiteaudio.com

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.



Re: at-mime and at-url

2011-11-28 Thread Dan White
On Fri, Nov 25, 2011 at 9:55 AM, Edward K. Ream edream...@gmail.com wrote:
 2. There may be significant interaction between @url and @mime.  That
 being so, it makes sense to make the @mime processing optional.

The @mime plugin's genesis was to separate opening of files on the
local filesystem from URLs and UNLs.
At the time, the UNL plugin would just call the webbrowser, which
explicitly had different settings than my '.mailcap'.
Also, KDE's kfmclient exec uses (used?) its own settings for
figuring out which program to use.

@mime's purpose is to simulate the behavior of double-clicking on the
file in a file-manager running under the current desktop system.
Terry's revision at 3860.3.1 pretty much made @mime obsolete through
using g.os_startfile on local non-leo files.

xdg-open, currently used for @url's with no scheme or file://, has
nearly identical behavior to @mime's default behavior.
@mime also allows re-defining either a different command to exec or a
function to handle the argument with an @setting.

Dan

-- 
SDG
www.whiteaudio.com

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.



Re: at-mime and at-url

2011-11-28 Thread Dan White
On Fri, Nov 18, 2011 at 5:26 AM, Josef joe...@gmx.net wrote:
 Although it seems @url can under some circumstances also open local
 files with the associated program, @mime certainly does a more
 consistent job, particularly with relative path names.

Can you come up with an example where the behavior is different?  With
the current core handling of UNLs, the changes should be minor.

Dan

-- 
SDG
www.whiteaudio.com

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.



Re: at-mime and at-url

2011-11-25 Thread Edward K. Ream
On Fri, Nov 18, 2011 at 5:26 AM, Josef joe...@gmx.net wrote:

 I would be in favor of making @mime a default [plugin].

I would prefer not to do that, for several reasons:

1. In some cases, it's important to load Leo as quickly as possible.

2. There may be significant interaction between @url and @mime.  That
being so, it makes sense to make the @mime processing optional.

I'm willing to change my mind.  Given the number of bug reports
against @url, and the inherent complexities of URL's, some provably
solid approach is certainly needed.

For now, though, there are many more pressing issues to attend to.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.



Re: at-mime and at-url

2011-11-20 Thread Terry Brown
On Fri, 18 Nov 2011 03:26:09 -0800 (PST)
Josef joe...@gmx.net wrote:

 I would be in favor of making @mime a default package. It may even be
 possible to merge them into a unified @url, but because of the reasons
 just stated, that may not be desirable after all.

Hadn't heard of @mime - I think its advantages should be merged into
@url, I think @url treats the entire first line as the URL, so spaces
in the URL aren't an issue.

The other differences are probably related to how Leo decides between
opening the file itself vs. opening it with an external program.
Perhaps Ctrl-(double)click on an URL (in body or tree) should indicate
*always* load in external program, whereas unmodified (double)click on
an URL lets Leo decide whether to load itself or externally.

Cheers -Terry

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.