Tue.17:18:00 <+billnye> shabble: you consume french fried troll meat
Tue.17:18:22 <+shabble> dammit, where's my towel?
Tue.17:18:37  * shabble fumbles his nickname setting variable magic
Tue.17:18:51 <+billnye> being confused, you mispronounce the magic words
Tue.17:20:10 <+shabble> uh-oh
Tue.17:21:14  * shabble 's Irssi glows purple for a moment.
Tue.17:22:18 <+billnye> annnnd scene.
Tue.17:22:52 <+billnye> today's episode of Community Nethack Theatre has been brought to you by the letters d and f, and the number +2

Theme that screws with the usual /formats, like the GNU Screen variant.

Part of the init code calls statusbar prompt reset which causes collateral damage on things like visible, placement and type.

On startup, it should parse the output of statusbar prompt, and store these settings somewhere such that they can be restored at a later date.

feature_tests/getchan.pl has an example of how to handle the parsing.

If you join+ a channel on a server you're not connected to, and that server doesn't have a MOTD you will never join the channel.

Is a MOTD mandatory acording to the IRC spec?

(As per discussion with shabble)

I narrowed down my extended shutdown issue within irssi by manually unloading each script after leaving it running for a few days.

/script unload auto_server_ng hung irssi

Something that combines various features from logresume.pl (/logview, /logtail, etc), grep, listing available files (by network, channel/query...blah blah.

Maybe really sneaky and try to parse logs using existing formats to try to figure out how they should have been coloured.

Adding the vim_mode and vim_windows statusbar items to the prompt line with e.g.
/statusbar prompt add -after input -priority 15 -alignment right vim_mode
works only until irssi is restarted. The items are correctly saved to the config file but will not be visible or appear under items in
/statusbar prompt

Doing
/reload
will then correctly load and display the items.

Input handling of vim mode is currently a big ball of mud. Clean it up

Error:

Can't use an undefined value as an ARRAY reference at /home/.../.irssi/scripts/autorun/63-longify-urls.pl line 186. the closest link to that that I can find is: Link: yfrog Photo : http://yfrog.com/kh4q7p

Appears that https://yfrog.com/kh4q7p is actually a valid (non-shortened) link.

have selective ignore/or ignore-exceptions for things that happen to friends (maybe reuse notify list?) or people who have been active in a channel recently

Useful for spotting ask-and-run people before bothering to type, without the EPIC spam of global joinquits.

if you /j #foo on freenode, and freenode forwards you to ##foo, but you are already on ##foo, irssi drops you back into the channel window you were in to start with. this is confusing

you suggested you might write a script to fix this sometime if I reported it here.

if you do, i would be eternally grateful.

Jason

In irrsi, some windows are prefixed with q, w, etc. :b q does not go to the window. Moreover, if there exists a window prefixed q and a channel, quebec, it should go to q before quebec.

First: Thank you for this script! It really helps me a lot in coping with these stupid "short URLs" on wtitter and the like. Unfortunately I don't know perl well enough to fix the following problem myself, so I'm posting it here.

Currently longify-urls.pl seemingly also "resolves" URLs not listed in longify-urls.list:

http://t.co/AgHfYlq
is being resolved to
/artikel/C31315/ueberwachung-wir-leben-noch-frei-aber-nicht-mehr-lange-30685243.html
whilte the actual Location-Header sent by t.co says
http://www.faz.net/-025ATJ
while faz.net ist not listed in longify-urls.list:
% grep -q faz.net ~/.irssi/longify-urls.list; echo $?
1

(Also this shows that longify-urls.pl doesn't handle Location-headers starting with a slash correctly. It should prepend the known hostname.)

Could you have a look at this?

Thanks!

As the title states.

Idea

In some channels it's commonplace to correct your mistakes with a pseudo-regex, for example:

<Foo> I love badgers!
<Bar> Badgers, really?!
<Foo> s/badgers/horses/

Instead of mentally parsing it, get irssi to do it!

It needs some security and sanity checking for the replacement string, and should have a couple of thresholds / restrictions.
Something like:

• users can only modify their own lines
• items beyond a certain number of lines aren't touched
• items older than a certain threshold aren't touched
• s/a/b/g isn't allowed (but difficult to generalise - how little is too little. Maybe run the match and count the number of matches?
  • Only the first N possible matches will be applied?

Other notes:

• There should be a visual cue to indicate it's been applied (* at the start/end of the line, maybe)
• Do you remove the line which contains the replacement command?
• Have to ensure it only gets applied to actual message contents, not parts of the UI /formats (timestamps, nicks, etc)

See Also

https://github.com/shabble/irssi-scripts/blob/master/feature-tests/linehax.pl

/JOIN #평범한대화방 appears to display incorrectly in uberprompt as "[ImaginaryNet/#평범한대?]"

Confirm that utf-8 is being properly handled by the script, and that it's either an Irssi problem (c.f
unicode/colours in sbar items bug and sbar string length bug), or that it can and should be fixed.

Make http://scripts.irssi.org/html/cron.pl.html more better

• autoload stuff at startup
• use subcommands
• less horrible perls

a better version of hilight that uses perl regex rather than the horribleness of POSIX REG_EXTENDED.

Code from rl_history_search could be useful in other scripts. Modularise it along the same lines as uberprompt so it can
be used elsewhere. Also work out a way to make sure deps are loaded for scripts that need it.

In vim-mode, you can escape to command mode with "jj", this is great, but some people (including myself) use multi-character sequences instead; "jk" for example.

In vim, you can bind "jk" to Esc with this command
:inoremap jk <Esc>

Would be great to have this in vim-mode; I'll have a scratch around in the code, but I'm not with my Perl

When I enter ido-mode by pressing ^G, and leave it (by pressing ^G again or pressing esc), a random line (often the bottom one, but not always) is deleted from the current window (always from the visible portion).