• Activity
• New
• All activity
• Showing only topics with the tag "markdown". Back to normal view
1. First release of my native Markdown notes app, Notementum (v0.1.0)

Screenshot I posted a few days ago about a notes app I was working on called Notementum, and I'm happy to show you the first release (0.1.0). Installation instructions are available on the Github...

Screenshot

I posted a few days ago about a notes app I was working on called Notementum, and I'm happy to show you the first release (0.1.0). Installation instructions are available on the Github repo: https://github.com/IvanFon/notementum

There's still lots of things I'd like to add, both big and small, and definitely a few bugs here and there, but I've been going for too long without sharing it, and I find it's best to release as early as you can to start getting feedback, and perfect it later.

One things that's missing is documentation. I'd like to start on this soon, but I'm probably not going to share this anywhere other than Tildes just yet, so this comment will do for now :)

Right now, the app only runs on Linux. I'd like to add Windows support, and it almost works, the problem is that WebKit2Gtk, the embedded web view I use to show note previews, doesn't support Windows. I'm going to explore some other options in the future, whether that's figuring out how to compile it, or allowing other preview methods (user's web browser, PDF, etc.).

The app is also very much in alpha, so you shouldn't use this for anything important, there may be bugs that can cause you to lose some of your data. If you do use this for anything, make sure you backup your notes database.

If you want to use it, here's a wall of text on usage:

Usage

The notes database is located at ~/.notes.db. When you launch the app, it'll load it, or automatically create it if it doesn't exist. I'd eventually like to allow choosing different locations, but it's hard coded for now.

The interface is fairly simple. The leftmost sidebar displays a list of notebooks, and the "middlebar" displays a list of notes. Selecting a notebook will display the notes within it in the notes list. Selecting a note will open it in the editor, which is to the right.

To create a new note, press Escape to focus on the searchbar above the notes list, and start typing a title. If no existing notes are found, press enter, and a note will be created with the title you entered.

To rename a note, double-click on it in the notes list.

The editor has a toolbar with 4 buttons, from left-to-right:

• Toggle between editor and preview (shortcut: Ctrl+E)
• Assign the current note's notebook
• Delete the current note

The green circle all the way to the right turns into a loading indicator when you have unsaved changes. Once you stop typing for a few seconds, your changes will be saved, and it'll switch back into a green circle.

Notebooks

Notebooks aren't created directly, they're based on what notebooks your notes are assigned to. This means that, to create a notebook, assign it to a note. To delete a notebook, just delete all the notes contained within it, or assign them to a different notebook.

Clicking on the notebook toolbar button brings up this dialog. To create a new notebook, double click on <New notebook> and type in a name.

Attachments

The notes database also stores attachments. This means that the entirety your notes can be contained in your database. Clicking on the attachment toolbar button brings up this dialog. The toolbar allows you to upload an attachment or delete it respectively. Pressing Insert Selected will insert the image at your cursor in the editor (![](image.png)).

Theme

The screenshots show the app with my desktop Gtk theme, Arc Dark. On your desktop, it'll use whatever your theme is. It should look good with any Gtk theme, but at some point I may bundle Arc Dark with it.

The note preview currently has it's colours hard coded to look good with Arc Dark, so it may look a bit off on other themes. I'll try to sort that out at some point.

Planned features
• load/save database to/from different path
• Windows support
• note exports
• database encryption
• changing syntax highlighting theme
• note tags
• full-text search
• proper documentation
• more keyboard shortcuts
• integrated sync
• although you should already be able to use Git, Synthing, Dropbox, etc.
Boring technical stuff

The app was made with Python and Gtk+ 3. I've done this before and I really enjoy the development experience, especially with Glade to design the interface. There are still some Gtk features that I should really be using to make things simpler (GtkApplication, actions, and accelerators) that I'll be adding later.

The database uses sqlite 3. This is convenient, as it allows for storing everything in one file, and will make fast searches easier in the future. Attachments are stored as base64 directly in the database. This makes it easy to have all your notes be contained entirely in the one database, but I may have to think about a more efficient method in the future.

Markdown rendering is done using mistletoe, which has been great to use. Syntax highlighting and MathJax renderers were already available, so it was just a matter of combining both and adding custom image loading from the database, which was very easy. Mistletoe has a very easy to use API, so this was no problem.

For LaTeX math rendering, I'm using MathJax. It supports pretty much everything, which is nice, but it can take a while to load. I'm currently loading it from a CDN in a <script> tag, so I'm hoping once I load it from a local file it'll be a bit faster. If not, I may have to find another solution.

Like I said, the app still has a few bugs that need to be fixed. If you find any problems, it would be great if you could leave a comment here or open a Github issue (or if you have any feature requests).

zettlr.com
3. Comparing Textile vs. Markdown for mobile use

gkayaalp.com
4. Tildes should not use hard line breaks for line endings

I'm new to Tildes, but I've been using Markdown-based comment systems for more than a decade: both Reddit and GitHub. My programming blog has been written in Markdown for the past 8 years. Overall...

I'm new to Tildes, but I've been using Markdown-based comment systems
for more than a decade: both Reddit and GitHub. My programming blog has
been written in Markdown for the past 8 years. Overall I've probably
written several novels worth of content in Markdown in my life.

I've already noticed that Tildes has made a serious mistake in its
handling of line endings: All line endings are treated as hard line
breaks
. This diverges from CommonMark and most uses of Markdown in
practice. If I wanted a hard line break, I'd put two spaces at the end
of the line, as specified by both CommonMark and the original Markdown.
Line endings should be otherwise be soft.

GitHub made the same mistake with its "GitHub-flavored Markdown," though
fortunately this mistake has been limited to issues. GitHub README.md
files don't have this behavior, nor does GitHub Pages. It the only other
Markdown system I've used with this flaw.

Why does this matter? If I'm writing more than a single sentence, I
never edit my comment inside my web browser. I edit it using my text
editor of choice, Vim, since it's far more comfortable. I don't even
have to copy-paste the text between applications. Instead, I have an
add-on, Tridactyl, that does this seemlessly and effortlessly.

Hard line endings just don't work well with long prose — exactly the
type of content that Tildes is encouraging — particularly when edited in
a proper text editor that knows about paragraphs and can do its own line
wrapping. Editing long lines is annoying and takes extra care. That's
why we have soft line endings after all.

I'm leaving all my line endings in this post so that you can see the
mess Tildes makes with it, with the ragged right-hand side due to font
differences. If I had written this in nearly any other Markdown system,
the text would have flowed into the page without issues. It is a mistake
for Tildes to do differently. This sort of compatibility issue is
probably going to be annoying enough to keep me off the site.

5. Need help formatting on Tildes

I have just posted on ~sports the last results of the major European soccer leagues, but it does not show as I'd want to. I read the Formatting help page, but I did not find an aswer to my...

I have just posted on ~sports the last results of the major European soccer leagues, but it does not show as I'd want to. I read the Formatting help page, but I did not find an aswer to my question, so if someone would like to help I'd appreciate it.

Basically I would like the post to look like this: Imgur link, but in the end it looks like the spaces I put in there do not show as you can see here: Imgur link.

Is there any way to make the post looks like what I want? I read about the Tables section in the Formatting help page, but I do not need a bold header row, which looks like a requirement for a table.

Thanks in advance for the help

6. Markdown for strikethrough and tables is now enabled

Previously, the only way to do strikethrough or tables on Tildes was by using HTML. I've updated the markdown parser now so that it supports the methods of doing them through markdown. The...

Previously, the only way to do strikethrough or tables on Tildes was by using HTML. I've updated the markdown parser now so that it supports the methods of doing them through markdown. The Formatting help page on the docs has been updated as well with info about how they work.

I don't think there should be any conflicts between strikethrough and linking to groups, but it's possible that there are some weird edge cases, so please let me know if you notice anything. Generally, strikethrough requires you to have two tildes both before and after the text you want to strike out, whereas group links will only have one before. So something like This ~~should work~~ doesn't work will result in should work instead of a link to a group named ~should.

7. Alternatives to Markdown for writing short documentation/TODOs?

Hi guys, I often find myself writing small text files for projects, like a bit of documentation or TODOs. I have a proper system in place for larger projects, but would love to be able to scribble...

Hi guys,

I often find myself writing small text files for projects, like a bit of documentation or TODOs. I have a proper system in place for larger projects, but would love to be able to scribble down things for larger ones.

As big of a fan of Markdown as I am, I find that it's often inappropriate for these kinds of tasks. For example, I find myself mimicking a task list with multiple-paragraph list items.

What do you guys use? Do you know of any Markdown alternatives that give you a bit more control over the layout?

Thanks!

8. Markdown

So I've been having a slightly off-topic discussion on a thread here and figured this would be a good subject to have wider input on. I don't think markdown adds anything to Tildes and I think it...

So I've been having a slightly off-topic discussion on a thread here and figured this would be a good subject to have wider input on.

I don't think markdown adds anything to Tildes and I think it actually degrades the experience for new users. Right now we're mostly old experienced reddit users and mods, but that hopefully will change. To me, markdown adds a not insignificant hurdle to formatting. Markdown has very few uses besides reddit and Github, and even then there's a few different types.

I suggest a WYSIWYG text box with a tabbed HTML option for those who want to use code formatting. Let's use something that's standard and encourages users to learn useful code.

Tell me why I'm wrong Tildes!

Edit: I primarily use mobile, so maybe that's part of the disconnect here. But it seems I'm the only person who cares and still thinks markdown is almost useless. I'm fine being in the minority. I still feel it's a good idea to look beyond the bleeding edge to the time when there's 300,000 or 3,000,000 uses.

Have a good day everyone!

9. [Extension] Markdown live preview for Tildes

Hacked together a simple markdown live preview, which works for both comments and also new posts submission. To use, just install the extension and start typing on Tildes, you will see live...

Hacked together a simple markdown live preview, which works for both comments and also new posts submission.

To use, just install the extension and start typing on Tildes, you will see live preview. No settings to configure.

The code is open source and released under MIT. I am not really a JS dev, so any feedback is welcome.

10. Apologies if this has been requested previously: is there a possibility of a comment preview?

I'm not very adept with markdown, and it's helpful to see what my comment will look like before I post it with my borked formatting.

11. Text formatting: Escaping tildes or ats

I don't think this is super high priority, but it'd be nice to be able to escape the ~ or @ symbols so that something isn't automatically turned into a link to a group/user. For example, I noticed...

I don't think this is super high priority, but it'd be nice to be able to escape the ~ or @ symbols so that something isn't automatically turned into a link to a group/user. For example, I noticed in a comment I made that ~ers gets automatically turned into a link to the non-existent 'ers' group. I think if I write \~ers then it should not be linked. (E.g. ~ers)

12. Feature Request: Markdown preview

I'm not sure if it's a vanilla reddit feature or if it comes from RES, but I've become reliant upon the preview that shows up under a comment box that renders your response through markdown so you...

I'm not sure if it's a vanilla reddit feature or if it comes from RES, but I've become reliant upon the preview that shows up under a comment box that renders your response through markdown so you can see the formatting before you post it. This doesn't need to be real-time, since that would likely detract from the "lightweight" technical goal, but I feel like it might be useful

13. Text Formatting UI Possibilities

Markdown editing can be frustrating for some, and can be time consuming. A UI where the user simply clicks, types, then clicks again to end the formatting will be necessary, especially for those...

Markdown editing can be frustrating for some, and can be time consuming. A UI where the user simply clicks, types, then clicks again to end the formatting will be necessary, especially for those on mobile.

I'm unsure as to if a solution to this is already in the makings or not, but I made 2 options that would fit in with the current design for posting text.

On the side seems like it would flow well, and is easy to read.

On the bottom next to "Post comment" allows for many more options for markdown, even color (if that's possible).

Anyone else could make their own version of this and share it, just to get ideas out there.