Always says mark is overwritten

[mkleehammer]

Small thing, but when binky-overwrite is true, setting a mark always results in the message "Mark is overwritten", even if the mark did not exist before.

Great package, thanks.

[liuyinz]

fixed, please check it.

[mkleehammer]

That actually broke saving:

• mark a - nothing in echo area, good
• move and mark b - says mark a already exists and does not set mark b

You can now only set the first mark.

[liuyinz]

@mkleehammer , whether two manual records are considerd as duplicated is determined by binky-distance. If you like, set it to 0, and then only marks on the same line are seen as duplicated.

binky.el/binky.el

Line 96 in a860fe2

(defcustom binky-distance 5

[mkleehammer]

It seems to be working now, but I really thought I tested it by trying to set the 2nd 'a' mark in a completely different buffer.

Anyway, there is a related behavior that makes it feel a bit off. When it overwrites, it shows the message first, which has a delay, then pulses. I know what it is doing, but it makes it feel broken or that the pulse came out of nowhere.

Swapping lines 935 & 936 fixes it. Everywhere else the pulse happens before the message.

[liuyinz]

Thankes for reporting experience! I adjust the order of message and highight, please test it again.

[mkleehammer]

Looks great. Thanks for this package. The jump display is great, especially the inclusion of the project. I have two projects that share a ton of filenames, so that is helpful.