Fri 02 Dec 2011 04:08:55 PM UTC, comment #4:
sorry, i have try again, but it's not appear...
i'm also a programmer, so, if it appear next time, i will report more detail to you.
thanks very much :-)
|
Fri 02 Dec 2011 03:47:50 PM UTC, comment #3:
The ruby warnings are fixed in devel version (you can try it now, it's stable). So it will be part of future version 0.3.7.
For your crash, please tell me exact action to reproduce it. As I said, the WeeChat core buffer can not be closed. So I need the buffer name, and if possible the trace using gdb.
Thank you!
|
Fri 02 Dec 2011 03:33:29 PM UTC, comment #2:
sorry, i'm first to use savannah, so before msg may be lose.
i forgot the detail name of buffer which i had close, but, as you saied, may be weechat.core.
another question: i use archlinux, but it's default python is 3.x and ruby is 1.9.x. so weechat when up, it's give a lot of warning msg as:
----------------------------------------------------------
23:21:36 weechat =!= | ruby: stdout/stderr: NOTE: Gem.latest_load_paths is deprecated with no replacement. It will
| be removed on or after 2011-10-01.
23:21:36 weechat =!= | ruby: stdout/stderr: Gem.latest_load_paths called from (eval):14.
23:21:36 weechat =!= | ruby: stdout/stderr: NOTE: Gem.all_partials is deprecated with no replacement. It will be
| removed on or after 2011-10-01.
23:21:36 weechat =!= | ruby: stdout/stderr: Gem.all_partials called from /usr/lib/ruby/1.9.1/rubygems.rb:603.
23:21:36 weechat =!= | ruby: stdout/stderr: NOTE: Gem.all_partials is deprecated with no replacement. It will be
| removed on or after 2011-10-01.
23:21:36 weechat =!= | ruby: stdout/stderr: Gem.all_partials called from /usr/lib/ruby/1.9.1/rubygems.rb:603.
23:21:36 weechat | fifo: removing old fifo pipe "/home/walle/.weechat/weechat_fifo_1139"
23:21:36 weechat | Plugins loaded: alias, aspell, charset, fifo, irc, logger, lua, perl, python, relay,
| rmodifier, ruby, tcl, xfer
----------------------------------------------------------
so, weechat may need to update this for new python and ruby version. thanks vv much for you work to give me a so good software for life. good luck :-)
|
Fri 02 Dec 2011 03:21:02 PM UTC, comment #1:
Hi,
There is no buffer beginning with "irc.core." (except if you have an irc server called "core").
So please tell me what is the exact name of buffer you are closing, name can be for example:
core.weechat (this one can't be closed)
irc.server.freenode
irc.freenode.#weechat
Moreover, I will need the backtrace with gdb, please look at doc for doing that: http://weechat.org/files/doc/devel/weechat_user.en.html#report_crashes
By the way, many crashs can be caused by scripts, so your list of scripts is welcome too (and please try without any script loaded to be sure it's not a crash caused by a script).
For your second question, please join #weechat on irc.freenode.net for help, this bug is not the right place to ask ;)
|
Fri 02 Dec 2011 03:06:22 PM UTC, original submission:
when i close the irc.core.** buffer, weechat crash after a few minutes, i don't know why, so upload my crash log here FYI.
ps.
can weechat can highlight user nick list for different stat? may be red for online, blue for offline, something eles.
|