Modify ↓
Opened at 2011-07-12T17:49:45Z
Closed at 2012-03-12T23:51:17Z
#815 closed defect (duplicate)
identify -noload doesn't work with /oper
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BitlBee | Version: | devel |
| Keywords: | identify | Cc: | |
| IRC client+version: | irssi 0.8.14 | Operating System: | Linux |
| OS version/distro: | Ubuntu Linux 10.04 |
Description
"identify -noload" doesn't work if the password is not specified with the command directly. This should pretty much explain it all:
19:44:36 -!- Mode change [-R] for user The-Compiler 19:44:36 -!- You're now known as foo 19:44:36 <@root> Changing nicks resets your identify status. Re-identify or register a new account if you want your configuration to be saved. See help nick_changes. 19:44:40 -!- You're now known as The-Compiler 19:44:46 <@The-Compiler> root: identify -noload 19:44:46 <@root> About to identify, use /OPER to enter the password 19:44:51 -!- Trying to identify 19:44:51 <@root> You're trying to identify yourself, but already have at least one IM account set up. Use identify -noload or identify -force instead (see help identify). 19:44:59 <@The-Compiler> root: identify -noload mypassword 19:45:00 -!- Mode change [+R] for user The-Compiler 19:45:00 <@root> Password accepted
Attachments (0)
Change History (4)
comment:1 Changed at 2012-01-26T10:20:45Z by
comment:3 Changed at 2012-02-01T05:40:27Z by
Oh, wait.
I just tested with identify -noload instead of a regular identify so I can't tell for sure what it did.
Since one can change nicks now, is there any reason identify -noload should still exist? :P
comment:4 Changed at 2012-03-12T23:51:17Z by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
#814 is similar.
Note: See
TracTickets for help on using
tickets.

This seems to be fixed for quite a long time already ;) Seems like I can't close it :o