-
Notifications
You must be signed in to change notification settings - Fork 28
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
Autocomplete page name to make link doesn't work as expected #10
Comments
Hi @DuendeLogico! For a), are you aware of any pattern to this behaviour? I have only ever seen it create the menu as expected. b) It would, of course, be better to not be able to select as an option. I'll keep it in mind and see if there's a quick fix for it. However, this doesn't feel like a critical problem for right now. c) Would definitely be nicer to be able to click this as well as select it with the mouse. I'll look into changing that. |
Hi, If I understand right, for a), I find it works only when new a default tiddler with type as "content type" as below: If I new a markdown tiddler or others, or change the type from 'content type' to md and others, then nothing will happen... I like this tiddlyroam a lot, hope this can work for md as well:-) |
Sorry, coding and Github ignorant here.
In Roam, when you put a "[[" and start writing a page name, a contextual box appears just down of the cursor, and you have the option to autocomplete the full page name, and it's very useful, because it's a very fast way of creating an internal link (also, you only have to remember the name partially).
In TiddlyRoam, in the same situation:
a) sometimes, nothing happens (!).
b) when the box appears, before or after all the possible page names, an horizontal line appears. If you choose that line with the down arrow, a literal "<hr>" appears in the final page, which doesn't make sense.
c) I learned after some time that you can choose the page name in the box with the down arrow. I was trying to choose it with the mouse, as in Roam, but that doesn't work
The text was updated successfully, but these errors were encountered: