Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Add function to open first found URL in tweet #39

Open
mkaito opened this Issue Apr 28, 2011 · 4 comments

Comments

Projects
None yet
2 participants

mkaito commented Apr 28, 2011

Many tweets will have a link in them, and tabbing through "things" until I reach the URL to open it with Enter, can get tedious after a while. You already have "twittering-next-thing" or similar, bound to TAB, maybe a modified version could automatically "tab" until it finds a url and open it?

Collaborator

cvmat commented Jun 26, 2011

I have commited twittering-goto-next-uri and twittering-goto-previous-uri. By using them, you can jump to the next/previous URI explicitly written in a tweet. The functions ignores things except explicit URIs.
In addition, twittering-goto-next-thing and twittering-goto-previous-thing with a prefix argument by "C-u" perform similarly.
How about the functions?
I think that automatically opening it is not good way because which URI will be opened is not necessarily obvious.

mkaito commented Jun 27, 2011

I'm not sure what you mean by "not necessarily obvious". The URL opened should be the first URL found in the tweet body?

Collaborator

cvmat commented Jul 10, 2011

Sorry for late response.
I meaned that the first URL may not be displayed when the command is invoked.
I think that searching a target and invoking an external program should be separated.
Does the command in your idea have no effect on a tweet without including a URL?
If so, it has different behavior than twittering-next-thing. If not so, it is very possible to open undisplayed URL.

mkaito commented Jul 10, 2011

It should indeed behave like you state. If the tweet on the current line doesn't contain a valid URL, the command should not do anything. This means, when searching for a URL to open, the function should not search beyong the currently highlighted tweet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment