version 0.9.6.0 preview #2 is available

[josip]

Notes for Writemonkey 0.9.6.0 preview #2:

- added: Complete Markdown support. See: http://daringfireball.net/projects/markdown/syntax
The only exception is emphasis syntax (*bold*, _italic_,
__underline__). Or should I drop that and go with a standard
(*italic*, **bold**)?

- added: Setting to enable or disable web links auto detection. See:
Preferences / Misc / Other. Disabled by default.

- added: Segment focus now also works with (==, --) heading markup.

- added: Bookmark segment focus. Hit CTRL+SHIFT+F6 to show text
between two bookmark strings.

- changed (experimental): When entering segment mode, caret is
positioned at the top of the segment text, not at the end like in
preview #1. Less confusing? Is it better? You can hit CTRL+END to
quickly move caret at the end of the segment ...

For complete release notes see:
http://groups.google.com/group/writemonkey/browse_thread/thread/bc2334e4d059caed

[Chris Lott]

A few notes on the latest release:

1) Personally, I vote for the Markdown standard of *italic* **bold**
and _italic_ __bold__ -- underlining is meant to indicate italizs
anyway, and if a client can't show italics than it would presumably be
smart enough to use underlines instead?

2) I know text area markers can be turned off, but is there any way we
could get the old ones back as an option or something? I really don't
like the new ones!

3) This may have been mentioned before, but any chance of having a way
to export settings? Related to that, if I could specify where the
settings were stored, I could have the settings saved on a
synchronized drive so my WM settings would be synced between computers
auomatically.

I know some of my other suggestions/bug reports have been filed
away... I appreciate your continued development. WM just gets better
and better and better!

c

[josip]

I'll probably go with the Markdown emphasis standard. There is no real
need for underline anyway.

About markers - no old markers I think. I honestly think that new ones
re better.

There is a way to export settings (F9). But there is no automatic
sync. It could be done though. On to-do list but not very high.

There are so many (excellent) suggestions and also some bugs and
inconveniences to deal with ... and so not enough time. I'll do my
best.
i.

[h]

I admit that its less "conventional" in some regards but *bold*
_italic_ are fairly common/have been common in a lot of text-based
circles over the years. It's not a huge deal to adapt to one or the
other but I having the option to use it would be nice. Underline
is... I can't really imagine a need for it, as I've never utilized it
in any basic writing format, so double underscore would make sense
there.

I suppose its just for the minor economy and convenience of keeping
bold and italic cut back to just one character and separate ones. It
looks a bit better in raw text form visually, as well, in my mind.

I don't suppose it's possible to include an option to toggle between
the two?

[josip]

I totally agree with you. It is why I broke the Markdown standard. But
it is standard nevertheless and one does not gain much by breaking it.
Hmmm, maybe I should put a new tab in the preferences - markup options
and allow user to choose preferred style.

But everything could not be customizable. The decisions must be made
and not everyone will be happy about them. Like corner marks. I cloud
make old ones as an option. But I won't.
I.

[Murray]

One interesting outcome from implementing Markdown that might cause some confusion to users is that Markdown interprets an indent as the beginning of <pre><code> content. This means that any Markdown markup in a paragraph that starts with an indent won't be processed as markup content, but will be left in the unprocessed form.

May be something to keep in mind if users ask why markup export isn't working, or is only working erratically.

M is for Murray
http://www.voodoologic.org