itch.io

could that be the issue?

I think it’s possible but can’t say for sure, unfortunately.

Will setup a VM on my free time and test if it could fix it or not

Thanks, let me know when you do!

Hi,

I don’t have any experience with AtlasOS, or what might be causing issues in that stripped down environment. Do you have Printing enabled?

https://docs.atlasos.net/getting-started/post-installation/atlas-folder/general-configuration/#printing

Hi, thank you for the report and the logs!

I unfortunately do not have an m2/sonoma device to try to debug this issue, but am hoping to borrow or rent one.

I don’t think it would help, but can you see if you also get the same crash in the universal build, but using open using rosetta?

Of course not. This is true for any digital content you buy, ever.

?

Thanks for the feedback!

What do you see as the advantage of minimizing to the tray, vs just minimizing?

I considered adding it early in development, but since it doesn’t really “do” anything in the background that you’d need to be notified about, it was never added.

Hi!

Thanks, I don’t think you’re missing anything, and both of these issues should get a fix.

Note that page breaks are only be visible in the exported PDF, not in the preview or in the editor.

Hi,

Thanks for attaching the markdown file, that makes this much easier!

I see several duplicate headings in the attached file:

• ->For X:<-
• ->For Y:<-
• ->Gravitational Force<-
• ->Equation of Motion<-
• ->Wavelength<-
• ->Power<-

These all appear twice, but they are under different parent headings.

If you don’t want to use the rule at all, you can disable it with:

"no-duplicate-header": false

in the “Markdown formatting rules” in “Preferences -> Advanced”.

If instead, you want to treat headings as unique if they’re under different parent headings (so that you can have Change in Position -> For X: is not the same as Final Velocity -> For X:, you can enable the allow_different_nesting parameter for the no-duplicate-header option instead:

"no-duplicate-header": {
  "allow_different_nesting": true
}

Hope that helps!

Hi, nice find!

I can reproduce the issue, and hopefully can get it fixed.

PS: Is there an option to change the type of highlighting (color, shape) in the preview ?

No, not at this time

Hi,

As you may have guessed, Deepdwn has no support for adding custom markdown elements, or removing the default ones. It would be very complicated to do so, and isn’t in scope for possible features in the future.

I don’t have great suggestions for your use case, but I would probably use <u>underline</u> and the existing strike through to represent your underlines and unreadable text, and then (if needed) style them as you like outside of Deepdwn, assuming you intend to host/display the digitized output somewhere.

Hi,

Yeah, there’s no character ruler implemented currently. I’ll add it to the “features I’d like to add” list, but not ETA on that currently :)

Hi,

The selected folder is in the sidebar under “folders” at the bottom. You can remove the current folder if desired, and/or add additional folders there.

Hope that helps!

I’m less confident that generated IDs would work for duplicated headings across files?

That’s certainly supported within Deepdwn, yes

FWIW, I also noticed that the syntax checker complains about non-unique heading text. Is there an easy way to turn this rule off?

You can disable that syntax check in the config in Preferences > Advanced > Makdown Formatting Rules. You’d want to add

“no-duplicate-header”: false

Hello, and thanks for the feedback!

While custom heading IDs aren’t currently supported, the automatically generated ones are unique. Generally, you’d use

[my first brown bears heading](#brown-bears)

and

[my second brown bears heading](#brown-bears-1)

and so on.

I believe there may be an issue with autocomplete which may by obscuring that feature as well, so I’m hoping to get the fix out for that soon.

Hi, developer of deepdwn here.

I’ve been using Textreme 1 and 2 for years and love them both also!

Thank you!

There is an issue with the description section of your document.

It needs to appear like this (with the key and content on a single line)

description: Organizing potential quests and story

or like this (with the content indented on the following line):

description:
  Organizing potential quests and story

Otherwise, the yaml section is technically invalid, and Deepdwn is unable to parse the metadata (in some circumstances), and you don’t get the correct title/tag/category display.

There is an advanced feature that ought to have been able to help with that (Settings > Advanced > Enable markdown format warnings), but I see that it has a bug preventing it from working correctly in the latest release.

If it was working, you might have seen this cryptic message, which may or may not have helped anyway.

Also I'm a little unclear on where tags from within the document show up, how you'd make tags akin to the chapter 1, chapter 2, etc shown in a screenshot on the product page, and how those differentiate from the outline tab.

Tags in deepdwn exist at the document level only, to help organize files together which share the same tag. 

In the product page screenshot, there are multiple markdown files (titled "chapter one", "chapter two", etc) which all have a common tag in their document metadata.

Hope that makes sense. Let me know if you have any questions about it!

It looks like your document's frontmatter isn't being parsed at all. Can you share the file you're having trouble with?

I'm not sure what you mean about aspect ratio scaling, as I would expect all scaling would maintain the original aspect ratio

Thanks!

I have, but (even ios aside) I don't think it fully meets my needs:

• Switching to fullscreen should require interaction (even if it can be used programatically), because it affects device navigation. So this means clicking possibly very small buttons.
• It may force landscape mode depending on device, which the user may not want, and usually hides native navigation buttons/menus.
• Fullscreen seems to cut off part of the deck display on small screens (ex: if width is < 512px)

For web-decker, are there plans to allow (probably blurry) non-integer canvas scaling?

On small screens, the locked sizes can leave a lot of unused space (and tiny elements), that could be better used by filling the screen with the deck, even at the cost of correct pixel scaling. 

The canvas scale itself can be overridden with CSS, but mouse event locations will be incorrect because of it.

I don't think new character strings will be added after headings, but double clicking heading prefixes to expand/collapse them will be added in a future version.

Technically, it's in the current version, but does not work correctly at all.

Thanks for the feedback!

This is something I have on my to-do list, but I don’t have any kind of ETA for you!

Hi!

You can fold headings right now!

Here’s the devlog where the feature was added, which has some extra information on usage: https://billiam.itch.io/deepdwn/devlog/270905/v0250-folding-pinning-file-monitoring-scroll-improvements

And the list of relevant shortcuts for heading folding when using the default key bindings: https://support.deepdwn.com/docs/guide/shortcuts/#folding

Hope that helps!

Do you have any plans to add the Raspberry Pi to the list of supported platforms?

Probably not any time soon. I don’t have a good way to incorporate an ARM build into the build and deploy process for raspberry pi, or a suitable device for performance testing/optimization right now.

So, you can certainly use Deepdwn to write your markdown for Nikola, and it won’t prevent you from adding arbitrary HTML tags and attributes to your document, but its preview isn’t going to interpret the markdown in the same way that Nikola/Python-MarkdownExtra does.

For instance,

<SECTION markdown="1">

## A level two heading
A paragraph with **bold** and *italics*.
</SECTION>

Will be interpreted the same as

<SECTION>

## A level two heading
A paragraph with **bold** and *italics*.
</SECTION>

Because Deepdwn doesn’t consider the markdown attribute on the section at all.

Also note the empty line after the section node, this is required in commonmark to interpret the following lines as markdown, instead of more HTML.

Hello!

I’m not totally familiar with Python’s (or PHP’s) markdown implementation, but my understanding is that, by default, markdown will not be parsed inside block level HTML elements there.

In general, Deepdwn’s goal is to meet the commonmark spec, where that is not the case. You can read about the way that mixed HTML and markdown are handled here: https://spec.commonmark.org/0.30/#html-block.

I think the spec isn’t especially easy to understand, but you can take a look at the examples below that, that are a bit easier to understand.

That said, Deepdwn limits the HTML elements and attributes that will appear in the preview and exports. That may be an issue for you, depending on your use case.

Hope that helps!

Thanks for the feedback!

PlantUML is unlikely to be added at this time, as it’s an external dependency that can’t be as easily bundled up with the editor.

I’d like to support some kind of external rendering tools at some point, so support may be added in the future, but there’s no time frame for that task.

Hello!

There isn’t a separate setting for the sensitivity currently. I believe it’s something like: sustained typing of 200(ish) characters, with no more than 10 seconds between each one. So, even typing slowly, you’d hit it eventually, but it depends a lot on the type of writing/editing you’re doing.

I’ll move this to feature requests!

Got it.

No, that’s not something that Deepdwn does currently. I’ll add it to feature requests

Hi,

There are some, but markdown doesn’t lend itself to autocomplete as much as other formats.

Offhand, Deepdwn supports autocomplete for:

• links to document headings
• footnotes
• relative links to images and other documents (and their headings)
• known categories and tags in the yaml frontmatter
• the yaml properties themselves that deepdwn uses (title, category, description, dir, pinned, tags)
• Mermaid chart names
• code autocomplete for some languages inside code blocks

Fountain documents support a number of common fields in the title page, characters and scene names, and some suffixes for those.

Is there some functionality you’re looking for, specifically?

Hi,

This has come up once before (with .mdx). My feeling at the time (but less so now) is that I think it’s misleading to appear to support these extended/dynamic formats, while still treating them as plain markdown files.

I may make that a setting, so that you can treat arbitrary filetypes as markdown (including rmd files), but I don’t hav an ETA for that change.

Hi, thanks for the feedback

Now, I’d really love to be able to do something with them as far as exporting them to an html list, or something. I’m not just tagging my files for my own amusement, I want to be able to publish the metadata somehow.

The purpose of supporting tags/categories in Deepdwn is more for organization within the editor, rather than a separate exportable item.

I don’t think there’s a general purpose thing that Deepdwn could do in that regard that would be useful to many people, without building a lot of features/configuration on top of it, but since the format used (markdown with yaml frontmatter) is reasonably standard (-ish, with caveats), I think somebody could build up tooling outside of Deepdwn to take that kind of thing on: It would parse your markdown files, gather tags and… do something with them, whatever it is that you need.

I’m of the opinion that you’re wasting time with the appimage and snap route

There are some issues with snap currently. It’s more like: If it works for you that’s great, but the appimage will continue to be supported, as it’s the one I use most currently.

I was under the impression that this app had linking to other notes built in

That is correct. You can:

• create markdown links to other documents, generally using relative paths.
• control-click those links to navigate to the linked document
• use the info panel at the bottom to see all documents linking to the current document.

Hope that helps!

For the font issue, you may try clearing your font cache, per this post: https://ekiwi-blog.de/en/25084/linux-snap-applications-error-with-fonts-only-rectangles-are-displayed/

fc-cache -r
rm ~/.cache/fontconfig/*
sudo rm -f /var/cache/fontconfig/*

Thanks for the feedback!

While the file:// protocol isn’t supported, both relative and absolute paths are, and you have a few options.

If your markdown file has been saved to /home/nigel/django/sarah/silsondb/static/site/my_file.md, you could use:

![image description](img/screenshots/quote-issue.png) to show the image.

For relative paths like this, you can also use autocomplete while typing the path (by typing Control+Space). This has some usage caveats: Your file must have been saved, and the images must exist somewhere inside your selected notes directory.

Lastly, you can drag and drop images directly on to the editor to create a markdown image with the path prefilled.

Hope that helps!

Hi,

The font issue isn’t unique to the 0.39 build, unfortunately, and I don’t have a solution for you (other than to use the appimage).

I believe it’s down to distro and desktop differences, but I don’t have a good lead on a solution.

Related post for this issue: https://itch.io/t/2130290/font-missing-in-file-explorer-on-linux-fedora-36-snap-package-install

I believe it’s D#, F, G, A#, C

Thanks for the feedback.

This may be added in a future update, but there are a number of preview formatting options I’d like to add at the same time.