[GH-ISSUE #4] [Feature Request] Replace wildcard tokens

bsakaguchi commented

2026-10-30 21:16:42 +00:00

Owner

Originally created by @horribleCodes on GitHub (Oct 13, 2022).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/4

Originally assigned to: @DominikDoom on GitHub.

Do you think you can make this script work with the wildcard tokens from this script as well?
The idea is twofold:
First, after typing __ (two underscores), you get a list of all available .txt files. Selecting one completes the token.
Then, the list changes from available token names to the items of that list. Selecting one replaces the token with the item.

So, as an example:

Entering __ shows a list of the wildcard files, like artist, adjective, style,...
Selecting adjective replaces the __ with __adjective__
A list of the content of adjective.txt is shown: angry,beautiful,dark,...
Selecting ´beautiful´ replaces the __adjective__ with beautiful

Originally created by @horribleCodes on GitHub (Oct 13, 2022). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/4 Originally assigned to: @DominikDoom on GitHub. Do you think you can make this script work with the wildcard tokens from [this](https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Custom-Scripts#wildcards) script as well? The idea is twofold: First, after typing `__` (two underscores), you get a list of all available .txt files. Selecting one completes the token. Then, the list changes from available token names to the items of that list. Selecting one replaces the token with the item. So, as an example: - Entering `__` shows a list of the wildcard files, like `artist, adjective, style,...` - Selecting `adjective` replaces the `__` with `__adjective__` - A list of the content of adjective.txt is shown: `angry,beautiful,dark,...` - Selecting ´beautiful´ replaces the `__adjective__` with `beautiful`

bsakaguchi added the

enhancement

label

2026-10-30 21:16:42 +00:00

bsakaguchi referenced this issue

2026-10-30 21:16:42 +00:00

[GH-ISSUE #1] config.json can't load #3

bsakaguchi closed this issue

2026-10-30 21:16:42 +00:00

bsakaguchi commented

2026-10-30 21:16:43 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 13, 2022):

It should be possible, I'll have a look at it. But I don't know how easy it will be to parse in my current implementation, so it'll probably take a bit of experimenting.

@DominikDoom commented on GitHub (Oct 13, 2022): It should be possible, I'll have a look at it. But I don't know how easy it will be to parse in my current implementation, so it'll probably take a bit of experimenting.

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@horribleCodes commented on GitHub (Oct 13, 2022):

From what I've seen, your parser should be able to read the data just fine - it'll just have a single column. I guess an array for the filenames and a two-dimensional one for the content should work.
You can use /\b_{2}(.*)\b/gU to match incomplete tokens, and /\b_{2}(\S*[^_])_{2}\b/gU to match complete ones.

@horribleCodes commented on GitHub (Oct 13, 2022): From what I've seen, your parser should be able to read the data just fine - it'll just have a single column. I guess an array for the filenames and a two-dimensional one for the content should work. You can use `/\b_{2}(.*)\b/gU` to match incomplete tokens, and `/\b_{2}(\S*[^_])_{2}\b/gU` to match complete ones.

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 13, 2022):

Yes, that part is fine. The tricky part is only autocompleting / changing the part of the prompt we are actively editing. For example, if the user has a longer prompt with keywords repeated multiple times, we only want to replace the one that is currently being typed by the user.

For normal tags this works well in the current implementation since after the hints close we are done with that tag. But for your suggested multi-stage wildcard selection, the window needs to stay open or re-open after the file selection, so I'm currently trying to implement a forced re-evaluation of that part for the autocompletion even though nothing changed (so the script still knows in which part of the prompt we want to change things). If I can get that part to work, the rest should be able to reuse the existing insertion code without much issue. If not, I'll have to do it a bit hacky with its own separate method that just replaces the results directly again.

@DominikDoom commented on GitHub (Oct 13, 2022): Yes, that part is fine. The tricky part is only autocompleting / changing the part of the prompt we are actively editing. For example, if the user has a longer prompt with keywords repeated multiple times, we only want to replace the one that is currently being typed by the user. For normal tags this works well in the current implementation since after the hints close we are done with that tag. But for your suggested multi-stage wildcard selection, the window needs to stay open or re-open after the file selection, so I'm currently trying to implement a forced re-evaluation of that part for the autocompletion even though nothing changed (so the script still knows in which part of the prompt we want to change things). If I can get that part to work, the rest should be able to reuse the existing insertion code without much issue. If not, I'll have to do it a bit hacky with its own separate method that just replaces the results directly again.

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@horribleCodes commented on GitHub (Oct 13, 2022):

Well, I thought it would be better if the prompt did change after the first selection - in case you want to just use the wildcard token, not a specific word.
In that case, you'd know exactly what changed, right?

@horribleCodes commented on GitHub (Oct 13, 2022): Well, I thought it would be better if the prompt did change after the first selection - in case you want to just use the wildcard token, not a specific word. In that case, you'd know exactly what changed, right?

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 13, 2022):

The multi-stage selection is definitely a good idea, yeah. Currently, it just wouldn't handle the case of a prompt like ... __wildcard__ ..... __wildcard__ since a simple regex comparison would replace both. So I at least want to try to use the what-changed-logic already in place. But if it doesn't work out, I'll probably just save the index to selectively replace.

@DominikDoom commented on GitHub (Oct 13, 2022): The multi-stage selection is definitely a good idea, yeah. Currently, it just wouldn't handle the case of a prompt like `... __wildcard__ ..... __wildcard__` since a simple regex comparison would replace both. So I at least want to try to use the what-changed-logic already in place. But if it doesn't work out, I'll probably just save the index to selectively replace.

bsakaguchi commented

2026-10-30 21:16:45 +00:00

Author

Owner

@horribleCodes commented on GitHub (Oct 13, 2022):

Have you considered using the cursor position?
https://stackoverflow.com/questions/2897155/get-cursor-position-in-characters-within-a-text-input-field/48150864#48150864

You could run back until the first separator, and perform the match from there. That way, the first match should be the relevant one.

@horribleCodes commented on GitHub (Oct 13, 2022): Have you considered using the cursor position? https://stackoverflow.com/questions/2897155/get-cursor-position-in-characters-within-a-text-input-field/48150864#48150864 You could run back until the first separator, and perform the match from there. That way, the first match should be the relevant one.

bsakaguchi commented

2026-10-30 21:16:45 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 13, 2022):

I already use cursor position for inserting at the right place. But I currently can't trigger autocomplete on a specific part, only the whole prompt at once which is then deconstructed into sections to find the actual text difference. So I'll probably just add an optional parameter to skip that step if we already know what changed and supply it.

@DominikDoom commented on GitHub (Oct 13, 2022): I already use cursor position for inserting at the right place. But I currently can't trigger autocomplete on a specific part, only the whole prompt at once which is then deconstructed into sections to find the actual text difference. So I'll probably just add an optional parameter to skip that step if we already know what changed and supply it.

bsakaguchi commented

2026-10-30 21:16:45 +00:00

Author

Owner

@evanjs commented on GitHub (Oct 13, 2022):

This is an interesting proposal

I currently use wildcards heavily with some modifications to allow for more "fuzziness" re paths (match file or directory), but those changes might not be necessary (or at least fundamentally different) if I could use wildcards against Danbooru directly.

This would be especially true if we could source tag groups

@evanjs commented on GitHub (Oct 13, 2022): This is an interesting proposal I currently use wildcards heavily with some modifications to allow for more "fuzziness" re paths (match file _or_ directory), but those changes might not be necessary (or at least fundamentally different) if I could use wildcards against Danbooru directly. This would be especially true if we could source [tag groups](https://danbooru.donmai.us/wiki_pages/tag_groups)

bsakaguchi commented

2026-10-30 21:16:46 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 13, 2022):

Alright, it took longer than expected to iron out all the bugs, but I'm pretty happy with the result:

https://user-images.githubusercontent.com/34448969/195632461-49d226ae-d393-453d-8f04-1e44b073234c.mp4

There is some catches though which I couldn't work around so far:

Gradio doesn't expose folders, only files. So the script needs an extra file which I simply called wildcardNames.txt. The script can only request the files based on their name there, but that also allows excluding specific ones if you don't want them.
Wildcards can contain spaces, but typing a space cancels the autocompletion, since you're starting a new word. So you can only search for single words at the moment. I might allow underscores as space replacements during wildcard search later, but don't have time for it today.

@DominikDoom commented on GitHub (Oct 13, 2022): Alright, it took longer than expected to iron out all the bugs, but I'm pretty happy with the result: https://user-images.githubusercontent.com/34448969/195632461-49d226ae-d393-453d-8f04-1e44b073234c.mp4 There is some catches though which I couldn't work around so far: - Gradio doesn't expose folders, only files. So the script needs an extra file which I simply called `wildcardNames.txt`. The script can only request the files based on their name there, but that also allows excluding specific ones if you don't want them. - Wildcards can contain spaces, but typing a space cancels the autocompletion, since you're starting a new word. So you can only search for single words at the moment. I might allow underscores as space replacements during wildcard search later, but don't have time for it today.

bsakaguchi commented

2026-10-30 21:16:46 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 13, 2022):

I pushed & released the changes just now, hope you enjoy!
Also, as per the notice in the readme:
Since not everyone has it, it's disabled by default. So you need to enable it in the config and edit the wildcardNames.txt file I mentioned above to add/uncomment your wanted tags.

@DominikDoom commented on GitHub (Oct 13, 2022): I pushed & released the changes just now, hope you enjoy! Also, as per the [notice in the readme](https://github.com/DominikDoom/a1111-sd-webui-tagcomplete#new---wildcard-support): Since not everyone has it, it's disabled by default. So you need to enable it in the config and edit the `wildcardNames.txt` file I mentioned above to add/uncomment your wanted tags.

bsakaguchi commented

2026-10-30 21:16:46 +00:00

Author

Owner

@horribleCodes commented on GitHub (Oct 13, 2022):

Thanks a bunch!

@horribleCodes commented on GitHub (Oct 13, 2022): Thanks a bunch!

Rows
Columns

[GH-ISSUE #4] [Feature Request] Replace wildcard tokens #1