viewMarkdown Support

Select the route that best describes your need. The page will focus on the relevant guidance and keep the subject field aligned with your choice.

Feature Requests

Use the form below for suggestions and improvement requests to editing, navigation, export, automation, documentation, or workflow ergonomics. Stronger requests are easier to evaluate and prioritize when you include the following points in your request.

Best requests Describe the current friction, the desired outcome, and why the change matters in real work.

Useful detail Include whether there is a current workaround and whether the request affects one file or an entire workflow.

Examples Commands, shortcuts, export behavior, sidebar behavior, table editing, and integration points are all valid request areas.

Reproducible Bugs

Use the form below to report bugs when the issue can be recreated with specific files, key presses, or steps, or when you want to expand on what happened, what you expected, and what conditions seem to trigger it.

Exception Reporting

viewMarkdown includes a reporting mechanism for exceptions that are caught by the application. The Report button in the Exception dialog sends technical diagnostics, not your working content.

No personal information or document text is ever sent to El Buho Consulting. The point is to help diagnose the failure using stack and environment detail only. If you want to inspect the diagnosis data, use the Copy Error button and then paste into the form below.

Before You Report a Bug

Check whether the same issue happens in a new temporary Markdown file.
Note whether it is tied to rich-text mode, source mode, or an export action.
Include the exact key presses if the issue is editor-interaction specific.

Information Worth Including

Version viewMarkdown version and Windows version.

Repro Exact steps, expected result, and actual result.

Scope Whether the issue affects rich-text mode, source mode, or both.

File sensitivity Whether it happens only in one file or in new files too.

Useful Attachments

A short sample Markdown file that reproduces the issue.
A screen recording when the failure is timing- or cursor-related.
A screenshot of the unexpected export result.
The output of viewmarkdown-cli.exe task-stats or file-state when automation is involved.

Paid Branding

We use Markdown as an intermediate file format during rapid prototyping. We customize viewMarkdown to highlight custom syntaxes for our reports. If we do work for you, we will likely integrate a custom version of viewMarkdown in the workflow.

If you are not our client yet, use the form below for requests on branded export work, custom documentation surfaces, theme styling, packaging guidance, rollout support, or company-specific behavior layered on top of viewMarkdown.

Examples Export theme customization, branded download pages, help-page integration, deployment guidance, and workflow refinement.

Best starting point Describe what must match your brand or process, what can remain standard, and what deadline or rollout context applies.

Engagement fit The form below is for work that goes beyond a general public issue report and belongs in a consulting conversation.

Self-Service Pages

If your question is really "how do I use this?", start here first. That is usually faster than opening a support request. You might even stumble onto a feature you did not know you needed.

Daily useUser Guide

Supported syntaxMarkdown Syntax Guide

ShortcutsKey Bindings

Images and exportImages and Export Themes