vimprobable-users

[Vimprobable-users] Showing destination link without mouse

[Morgan H. <mt...@gm...>]

I was getting caught up on some old items from the mailing list when I
came across this old thread:
https://www.mail-archive.com/vim...@li.../msg00234.html

I agreed with Karryana's idea that a way of showing a link destination
without having to switch to the mouse or yank to the clipboard would
be useful, as I know how irritated I was when the status bar
disappeared from my primary browser.

So, I've went ahead and implemented this, using the ";l" shortcut.
This included a minor refactoring to share code with the mouse hover
handling. Please see the attached simple patch and let me know if you
have any concerns or better suggestions.

Morgan

Re: [Vimprobable-users] Showing destination link without mouse

[Jason R. <jas...@gm...>]

On 19/09/14 at 03:40pm, Morgan Howe wrote:
>I was getting caught up on some old items from the mailing list when I
>came across this old thread:
>https://www.mail-archive.com/vim...@li.../msg00234.html
>
>I agreed with Karryana's idea that a way of showing a link destination
>without having to switch to the mouse or yank to the clipboard would
>be useful, as I know how irritated I was when the status bar
>disappeared from my primary browser.
>
>So, I've went ahead and implemented this, using the ";l" shortcut.
>This included a minor refactoring to share code with the mouse hover
>handling. Please see the attached simple patch and let me know if you
>have any concerns or better suggestions.
>

Thanks Morgan: this is a nice addition.

Cheers,

/J

-- 

http://jasonwryan.com/  [GnuPG Key: B1BD4E40]

Re: [Vimprobable-users] Showing destination link without mouse

[Morgan H. <mt...@gm...>]

Ping. Any feedback on this, or did it get lost in the weekend shuffle? :)

Morgan
On Sep 20, 2014 4:17 PM, "Jason Ryan" <jas...@gm...> wrote:

> On 19/09/14 at 03:40pm, Morgan Howe wrote:
>
>> I was getting caught up on some old items from the mailing list when I
>> came across this old thread:
>> https://www.mail-archive.com/vimprobable-users@lists.
>> sourceforge.net/msg00234.html
>>
>> I agreed with Karryana's idea that a way of showing a link destination
>> without having to switch to the mouse or yank to the clipboard would
>> be useful, as I know how irritated I was when the status bar
>> disappeared from my primary browser.
>>
>> So, I've went ahead and implemented this, using the ";l" shortcut.
>> This included a minor refactoring to share code with the mouse hover
>> handling. Please see the attached simple patch and let me know if you
>> have any concerns or better suggestions.
>>
>>
> Thanks Morgan: this is a nice addition.
>
> Cheers,
>
> /J
>
> --
>
> http://jasonwryan.com/  [GnuPG Key: B1BD4E40]
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.  Video for Nerds.  Stuff that Matters.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
> _______________________________________________
> Vimprobable-users mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vimprobable-users
>
>

Re: [Vimprobable-users] Showing destination link without mouse

[Hannes S. <ha...@yl...>]

Hi Morgan,

looks like a certain merge to me functionally. I'd just like to confirm
that there are no major redundancies (code-wise) with the yank function.

Thanks!

Hannes

Re: [Vimprobable-users] Showing destination link without mouse

[Morgan H. <mt...@gm...>]

Hey Hannes,

On Thu, Sep 25, 2014 at 1:18 PM, Hannes Schüller <ha...@yl...> wrote:
> looks like a certain merge to me functionally. I'd just like to confirm
> that there are no major redundancies (code-wise) with the yank function.

Aside from the show_link() function extracted from the hoverlink
callback, there was nothing that really stood out to me as terribly
redundant. I copied the same pattern in the script() function which
was already somewhat repetitive to begin with, but it looked like a
marginal gain to bother with cleaning up that function at the moment.
It might be worth trying to refactor that a bit at some point as it
will likely only get worse, but I didn't consider it too urgent or
belonging in this patch.

Regards,
Morgan