search

sawhney17 / logseq-smartblocks

MIT License
171 stars 12 forks source link

integrated setting is bugged #13

Closed lef-est closed 2 years ago

lef-est commented 2 years ago

Edit: I know mod stands for command in mac and ctrl in windows. The reason I tried to change it is because when I first tried ctrl+t, it was buggy. The blinking cursor disappeared but the search panel did not come up.

image If I access it via Settings > Plugin Settings > logseq-smartblocks, then it is buggy: I can't really type or change anything in the text box. I tried to change it, and the result is weird: The UI shows no change at all; and in settings.json it looks like I only managed to append one or two letters to the end or a random position in the original string.

image The setting here works. I needed to relaunch logseq but it worked in the end. The strange thing is the setting above (first screenshot) still showed "mod" for me, even though settings.json is already changed to ctrl.

sawhney17 commented 2 years ago

Yeah it's a bug with the current version of logseq, when the next version of logseq is release this bug will be fixed. On 15 Apr 2022, 5:42 PM +0400, lef-est @.***>, wrote:

If I access it via Settings > Plugin Settings > logseq-smartblocks, then it is buggy: I can't really type or change anything in the text box. I tried to change it, and the result is weird: The UI shows no change at all; and in settings.json it looks like I only managed to append one or two letters to the end or a random position in the original string.

The setting here works. I needed to relaunch logseq but it worked in the end. The strange thing is the setting above (first screenshot) still showed "mod" for me, even though settings.json is already changed to ctrl. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

lef-est commented 2 years ago

Great! I'll close this then.