A related issue is that the saved value of the "nick
completion suffix" does not remember leading spaces.
Ideally, I'd have the three characters: " - " [space,
hyphen, space] appended after a completed nickname. Since
there is an implicit space after the suffix (which is what
this bug is complaining about), I can set the prefix to just
" -" and it works ... for the duration of that session.
If I quit out of XChat and then restart it, the leading
space is forgotten, so now I have just "- " as the completion.
While they're two different bugs (and, looking at the
preferences format, it might be difficult to preserve
leading whitespace as I'd like), they were close enough that
I thought I'd just post here instead of opening a new bug.
Thanks!
tkil@scrye.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is indeed a problem.
I'll describe with a little more details.
Making sure nick completion wont add an extra space
character is easy and could be solved quickly, talking in
terms of <TAB> nick completion (not the auto nick completion
which is post processed after pressing <RETURN>).
Problem arises when you want to use a completer which has a
space in it's begining. for instance you want nick to
complete with " ,".
After changing to it, it'll work, but later on when saving
the configuration and loading it (closing and opening xchat)
it'll discard all spaces in the begining.
It is a problem and i'm still looking for a solution as the
ones i suggested zed are pretty ugly and patchy :
1. hardcode for completion_suffix, to grab also spaces at
the begining
2. never save extra spaces in other variables
3. specify which configuration variables should be treated
with spaces and which should spaces be chopped for.
Cheers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
A related issue is that the saved value of the "nick
completion suffix" does not remember leading spaces.
Ideally, I'd have the three characters: " - " [space,
hyphen, space] appended after a completed nickname. Since
there is an implicit space after the suffix (which is what
this bug is complaining about), I can set the prefix to just
" -" and it works ... for the duration of that session.
If I quit out of XChat and then restart it, the leading
space is forgotten, so now I have just "- " as the completion.
While they're two different bugs (and, looking at the
preferences format, it might be difficult to preserve
leading whitespace as I'd like), they were close enough that
I thought I'd just post here instead of opening a new bug.
Thanks!
tkil@scrye.com
Logged In: NO
Confirmed. Exists in X-Chat 2.4.1
Logged In: YES
user_id=139116
It is indeed a problem.
I'll describe with a little more details.
Making sure nick completion wont add an extra space
character is easy and could be solved quickly, talking in
terms of <TAB> nick completion (not the auto nick completion
which is post processed after pressing <RETURN>).
Problem arises when you want to use a completer which has a
space in it's begining. for instance you want nick to
complete with " ,".
After changing to it, it'll work, but later on when saving
the configuration and loading it (closing and opening xchat)
it'll discard all spaces in the begining.
It is a problem and i'm still looking for a solution as the
ones i suggested zed are pretty ugly and patchy :
1. hardcode for completion_suffix, to grab also spaces at
the begining
2. never save extra spaces in other variables
3. specify which configuration variables should be treated
with spaces and which should spaces be chopped for.
Cheers.