Skip to content
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

[FR} Naming block #44

Open
vasnt opened this issue Dec 23, 2023 · 3 comments
Open

[FR} Naming block #44

vasnt opened this issue Dec 23, 2023 · 3 comments

Comments

@vasnt
Copy link

vasnt commented Dec 23, 2023

It would be great, if block can be tagged/named & data can be exported by name/tag instead of copy & paste?

@heyman
Copy link
Owner

heyman commented Dec 23, 2023

I've been thinking about this a lot going back and fourth, and at the moment I'm leaning towards not having this feature. The main reason is that it goes against the scratchpadness of the program.

I can totally see the usefulness of such a feature, and it's definitely something that I would expect from a more traditional Notes app. However a large part of Heynote's appeal is it's simplicity, and if that is to remain so, I'm going to have to say no to a lot of actually useful features.

@alsoeric
Copy link

I like the simplicity of heynote, and I agree with most of your design decisions. I have a workaround for your no-tags rule that puts all the work on the user, not you. :-)

I take notes for different projects and clients for whom I need a key to search. My workaround is placing a hashtag in the first line of a block i.e. #client1 #sftp-depot. The built-in search is good enough for straightforward searching. Maybe having the capacity to filter by #tags would be a helpful addition.

Side comment: scratchpadness does not mean transient. I expect my heynote file to hit the 100MB point before a year has passed. Even though I will transfer a better-written version of the note to a more traditional document/note environment, I expect to leave the original note in context for future reference.

@porridgewithraisins
Copy link

porridgewithraisins commented Feb 2, 2024

Bumping this up, I really would like a search by tag!
For non-code content, I can just use the regex search feature and search by markdown heading.
But for code snippets/json, I would really like to have a tag feature.

It could be really dead simple, for example, I see that right now you're using
∞∞∞json as the sentinel separator.

What if here you accepted words until the newline as tags? Then existing ctrl+f will find it since this line is only visually hidden in the editor. So the only extra feature added will be a way to let people input it.

They don't even need to be shown, as the major usecase for this is if you have a really large document that is not easy to visually scan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants