Skip to content

Slash menu cannot be called after writing heading by using # #9022

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
3 tasks done
TaxDevOp opened this issue Aug 21, 2023 · 22 comments
Closed
3 tasks done

Slash menu cannot be called after writing heading by using # #9022

TaxDevOp opened this issue Aug 21, 2023 · 22 comments
Assignees
Labels
Milestone

Comments

@TaxDevOp
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Can the issue be reproduced with the default theme (daylight/midnight)?

  • I was able to reproduce the issue with the default theme

Could the issue be due to extensions?

  • I've ruled out the possibility that the extension is causing the problem.

Describe the problem

If i do a / ("Slash") the function menu is called. As soon as i do a "#", "##", "###" and so an, namely a header, the function menu cannot be called anymore by the / ("Slash").

Expected result

/ ("Slash") always calls function menu regardless of using Headers.

Screenshot or screen recording presentation

21-08-2023_15-38-26

Version environment

- Version: 2.10.0
- Operating System: Windows 10
- Browser (if used): not relevant

Log file

siyuan.log

More information

No response

@zxhd863943427
Copy link
Contributor

I am unable to reproduce your issue. Please close all plugins, code snippets, and switch back to the default theme before attempting again.

@TaxDevOp
Copy link
Author

Sorry to say this, but I didn't check those two checkboxes at the top of the form just for fun, confirming that I made sure
a) that I used the default theme and
b) no plugin was activated

I opened a new workspace where plugins are not trusted at all yet. To that extent, there can be no plugins here at all, and no themes either. I have filmed this again, the bug still exists. So it is in the code itself and is not influenced by third parties.

22-08-2023_09-03-21.mp4

@zxhd863943427
Copy link
Contributor

This is the situation of my test:
testheader
Maybe you can try upgrading and disabling the input method? Here is my device information:

- Version: 2.10.1
- Operating System: Windows 10
- Browser (if used): not

@TaxDevOp
Copy link
Author

TaxDevOp commented Aug 22, 2023

I now submit further evidence. I have now additionally recorded this bug on

So I have now shown this bug on 4 different devices with 4 different operating systems.
I had the idea that maybe it is due to different localization. I use German (DE), but as I show in the video with Fedora, it changes nothing, with English (US). By the way, I tried Fedora with both German and English. In both regions the bug remains. In the later videos i installed Siyuan completely new, so that from the outset it is clear that no themes or plugins can interfere.

@zxhd863943427
Copy link
Contributor

Is it possible to try Chinese? As far as I know, this is the language used by the developers.

@zxhd863943427
Copy link
Contributor

If you reopen this document, will the Function menu open normally?

@TaxDevOp
Copy link
Author

TaxDevOp commented Aug 22, 2023

Hi @zxhd863943427

tested both, but Siyuan dooesn't change its mind.

Test.chinese.mp4

@zxhd863943427
Copy link
Contributor

please try ((, [[, {{, #, / , :, This is other special input in SiYuan, if you can't call up the menu, it means that SiYuan should have a problem in this regard.

@TaxDevOp
Copy link
Author

TaxDevOp commented Aug 22, 2023

Hi @zxhd863943427,

the others work all as expected. It is isolated the "/" that causes trouble.
I could also work around some of the functions with the Settings > Keymap. But for example: "AI Chat" is not accessable through Settings > keymap (in other words: No possibility given to assign a shortcut like Ctrl+Alt+A or something like that). So as power user i am restarting Siyuan the whole day.
So there are two ways to solve this issue:

  1. Get "/" to work always or let me choose another hotkey for the function menu
  2. Bring all functions to Settings > Keymap so we can really access them. If "/"-menu has a bug, we are out...

@88250
Copy link
Member

88250 commented Aug 23, 2023

@achseu Please open the developer tool, and switch to the Console tab to check whether exist error logs.

image

@TaxDevOp
Copy link
Author

Hi @88250 ,

only a general Violation about an eventhandler "touchstart" is thrown with the start of siyuan:
image

But straight to the point: There get's no error thrown by using "/" after "#".
image

@monsterfurby
Copy link

Came here looking for this issue. I have encountered the same, also after a #-triggered headline. This only happens when in the same document and session, a #-headline was created. After restarting, the respective doc has the /-menu available again.

@TaxDevOp
Copy link
Author

TaxDevOp commented Nov 26, 2023

I am wasting my time by reopening siyuan the whole day since months. Wasted my money by paying for a livetime payment because i thought they "work hard" for their users. Here we see the truth: The tickets stay open for eternity and nobody gives a damn. If there wasn't such a lack of alternatives, I would have gone somewhere else long ago.
I asked them to allow a hotkey for the functions that you can't access caused by this bug, e.g. the AI - do you see it anywhere in the keymap? Nothing happens... For months.

@zxhd863943427
Copy link
Contributor

zxhd863943427 commented Nov 26, 2023

I'm sorry to make you feel this way, but it's really hard for developers to fix your problems at the moment. But the unfortunate reality is that if the developer's device can't reproduce your problem, they won't be able to figure out the cause of the problem and fix it. At present, developers are focused on two aspects, one is the more important synchronization corruption issue, and the other is database. Until there are enough error reports for this problem to allow developers to capture the location of the real problem, it can only stay open and wait.

@zxhd863943427
Copy link
Contributor

For hotkey, you need to open a new issue and list them in detail. As far as I know, this kind of request is usually passed very quickly.

@TaxDevOp
Copy link
Author

If you are already programming Markdown, you should use it. If we press "#", "/" is no longer usable. It's that simple. And now you want to tell me that if developers do the same, it won't happen? I have proven it on three operating systems, via video: MacOS, Windows, Linux. It doesn't work in all three systems, proven live on video.

The world works a little differently: if you don't take users seriously, no more will come, especially if they read lines like the one above. We're all fed up with big companies telling us all day long that "not enough other users" want the feature/bugfix and that's why it's not being delivered. This is exactly what drives us to OpenSource.
So, what do I listen to now with OpenSource?
Exactly the same thing: We don't care as long as not "enough" users want it. The fact that a) many users don't give any feedback at all and b) enough users drop out because of such bugs - these are not measurable figures, so they are simply swept under the carpet. So-called "dark figure". But if you don't care, it doesn't matter.

Good luck with this attitude. Keep the ticket open, it is a good warning for everyone who considers to buy this software.

@88250
Copy link
Member

88250 commented Nov 26, 2023

We are very sorry, but we are still unable to locate this bug. If there is any progress in the future, we will solve it as soon as possible. Thank you for your understanding and support.

@88250
Copy link
Member

88250 commented Nov 26, 2023

@achseu @monsterfurby Could you try it on the latest Chrome browser?

http://127.0.0.1:6806/

issue.webm

@88250 88250 changed the title Function menu cannot be called after writing headline by using # Slash menu cannot be called after writing heading by using # Nov 26, 2023
@88250 88250 self-assigned this Nov 26, 2023
@88250 88250 pinned this issue Nov 26, 2023
@88250
Copy link
Member

88250 commented Nov 26, 2023

We have pinned this issue so that more people can see it and help us locate it, thanks.

@zxhd863943427
Copy link
Contributor

If you are already programming Markdown, you should use it. If we press "#", "/" is no longer usable. It's that simple. And now you want to tell me that if developers do the same, it won't happen? I have proven it on three operating systems, via video: MacOS, Windows, Linux. It doesn't work in all three systems, proven live on video.

The world works a little differently: if you don't take users seriously, no more will come, especially if they read lines like the one above. We're all fed up with big companies telling us all day long that "not enough other users" want the feature/bugfix and that's why it's not being delivered. This is exactly what drives us to OpenSource. So, what do I listen to now with OpenSource? Exactly the same thing: We don't care as long as not "enough" users want it. The fact that a) many users don't give any feedback at all and b) enough users drop out because of such bugs - these are not measurable figures, so they are simply swept under the carpet. So-called "dark figure". But if you don't care, it doesn't matter.

Good luck with this attitude. Keep the ticket open, it is a good warning for everyone who considers to buy this software.

Unfortunately, despite performing these operations every day, I am unable to reproduce your issue. This holds true even in a virtual machine specifically modified for language modifications. If you pay close attention, you will notice that I have already posted videos of me performing similar operations above.

@Vanessa219
Copy link
Member

@monsterfurby Can you provide the input method, operating system, and Siyuan version information? Thank you.

@88250 88250 added the Bug label Nov 27, 2023
@88250 88250 added this to the 2.11.0 milestone Nov 27, 2023
@88250
Copy link
Member

88250 commented Nov 27, 2023

It seems to be due to a keyboard issue. German keyboards have this bug.

Are you using a German keyboard? @achseu @monsterfurby

Vanessa219 added a commit that referenced this issue Nov 27, 2023
Vanessa219 added a commit that referenced this issue Nov 27, 2023
@Vanessa219 Vanessa219 unpinned this issue Nov 27, 2023
@88250 88250 changed the title Slash menu cannot be called after writing heading by using # Slash menu cannot be called after writing heading by using # Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants