The preformatted style is indented a bit, which explains the indentation.
The backticks is just a shortcut to āturn onā the formatting. I donāt know how exactly you create that text, but if you type the backticks, then a space, then Test, then return and add the tags, it should all be in preformatted style.
The backticks have to be on the same line as the start of the preformatted text.
My solution was create a note, add a blank line, change it to pre-formatted, paste in the text. Which is far less messing about than altering the original text.
I typed 3 backticks then pasted the text, that just did the first line as shown in the screenshot.
What I should have done was type 3 backticks and then a space which activates the style and then paste the text. I missed the space.
That is better, but I would still like to be able to turn it off, I donāt use tags at the moment and the hash character is more use to me.
It would be fantastic if it was configurable whether Agenda converted hashes to tags by default or not. I never use Agenda tags, but I often use hashes, and so I always need to escape them by doing something like #this.
We would like to have some way to āescapeā special meaning, which might help you.
It would be unlikely to add a setting to turn this off altogether, because then you can get all sorts of strange effects if one device has it on and another off, or someone sends you a note with hashes. We would rather give a way to turn off the special meaning for a particular character, like you do with the inline text, but without actually changing the appearance.
Is that really what you want though? I assume you would rather just see the hash, with not other characters around.
What I would be inclined to do is to allow the backslash as a way to say āescape this characterā, but then Agenda marks the character as escaped and doesnāt use it for markdown. So the character would appear like other text, but be ignored for the markdown.
This I think would be much nicer than keeping the slash symbol in there. But maybe that is what you meant anyway.
The "\" character would effectively escape the following character as in C and other languages. So two backslashes would be changed to display just the one backslash, typing a backslash followed by a hash would show just a hash character overriding the default expansion.
That way we can quickly and easily type something that needs a special character, itās just a bit simpler and easier to remember.
Markdown etc are great but they can catch you out if you arenāt used to them (Iām not), so in the previous reply I did it by email, I suggested typing "\#" to get "#", but of course it displayed as "#=#" which is true but nonsense.
Cheers all,
(Loving Agenda, I bought the Premium and havenāt regretted it for a second. One of the best apps out there, coupled with Gladys they are my two favourites and both work across all the Apple devices).
Sorry it is frustrating you. The trick is indeed to use fixed width formatting for the hash tag. You can use the back ticks you mention to do that, or you can use the fixed width style available via the menus on Mac, and via the keyboard bar on iOS.
The reason we chose #tag to be a tag is that it is a very common pattern. Most note taking apps that support tags use this approach (eg Bear).
I understand that it is not something you are used to, but every user is different, and many are used to this convention. And many other users donāt use # other than for tags. (BTW type a # in a note here in the community, and note that you get a tag autocompletion. This community is standard software that we didnāt write, so it is a very widespread convention.)
In future. we would like to bring in a more systematic approach to āescapingā special meaning. That will help with using # where you donāt want a tag.
Note also that putting a space after the # will work in preventing a tag.
Another simple solution would be to have the string #text operate as a Tag, and # text operate normally.
This one could number paragraphs or processes as # 1, # 2, etc, and #text as a normal Tag.
Another solution would be to use the \ character in front of #1 or #2 to let the program know that the string following the \ character is to operate as normal and not as a Tag, and to then block the \ character from displaying in the text string.
Thus typing #2 would display as #2 but not function as a Tag.
Hopes this gives you some ideas. It is a lot simpler than some of the work arounds I have seen discussed.
