| Age | Commit message (Collapse) | Author | Files | Lines |
|
An item_id can now be passed as the optional argument to the `:Hackernews`
command which will load that specific item into the .hackernews buffer,
whether it be a story, poll, comment thread or individual comment.
Ex. `:Hackernews 9015621`
Close #35
|
|
Example comment [9720796]
|
|
|
|
:HackerNews commands needs `g:hackernews_stories` set before ftplugin code
is executed.
|
|
Exception only occurs when calling `:edit .hackernews` instead of
properly calling the `:HackerNews` command.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
From @alexluecke PR #8
Closes #3
|
|
The hackernews.link(external=True) function works better than the
default `gx` functionality. By default, `gx` will sometimes not work on
urls surrounded by brackets/braces/parenthesis, and will not work on
urls spanning multiple lines. The hackernews.link() function does not
have these issues.
|
|
Once you import a python module into an instance of vim it does not get
reloaded when a plugin manager updates the plugin. This can cause errors
when, for example, a new function is added to the python module and
updated vim code is trying to call it. This commit does two things:
1) Does not load the python code until the :HackerNews command is
called. There is no need to load the python code during vim startup if
the plugin will not be used.
2) Each time the :HackerNews command is issued and a .hackernews buffer
is opened the python code is reloaded to avoid the errors previously
mentioned.
|
|
|
|
|
|
|
|
|
|
|
|
|