Tuesday, March 4, 2014

Markdown editor for blogger

Markdown is quite popular these days and I like it for it’s simplicity. So I’ve been searching for a way to integrate it in my blog writing workflow. In Blogger, it’s unfortunately not an option.

There I could go:

  • either for WYSIWYG editor or
  • manual HTML writing.

However WYSIWYG generates too much HTML I don’t need. Moreover some pre-publish manual HTML editing is a pain then. And the other option I consider it rather slow/unproductive.

So, I looked for other options, and found stackedit.io. Even this post is (and couple others as well) written in it.

stackedit

I consider Stackedit great as it:

  • is Markdown editor,
  • is open source (see github repo),
  • has awesome UI (including live preview, key bindings, …),
  • has integration with other popular services that I use anyway:
  • has active community (just check the stars count and commit activity on the github repo) and
  • has impressive feedback time (resolution on my issues/questions came in couple hours)

So my post writing/editing workflow goes like this:

  1. write/edit post on stackedit.io,
  2. sync it to google drive and
  3. publish/republish it to blogger.

That’s it! No further in-blogger updates required!

Blogger specifics

Still there are some specifics in my workflow (to provide smooth blogger integration).

  • using the Interpreted variables: title and tags via:
---
title: Markdown editor for blogger
tags: blogger markdown stackedit.io
---

23 comments:

Peter Butkovic said...

would you mind raising an issue on: http://github.com/p6spy/p6spy/issues ?

Guest User said...

Someone did so already.
https://github.com/p6spy/p6spy/issues/200

Peter Butkovic said...

great! I thought it was you :)

Peter Butkovic said...

well, we might still need the additional input on the bug, would you mind providing it? (see the bug comments)

Lukas Eder said...

This is a good use-case for SQL-centric development, where you design compatible SQL schemas first and only then build Java applications on top of it. We've described this on our page here. The most demanding jOOQ customers have deployed jOOQ with a single application on Oracle, DB2, Sybase, SQL Server and H2. I think it would be quite hard to do the same with a domain-model centric approach (e.g. using Hibernate)...

Kurt Anderson said...

Thanks.

JoshuaMuheim said...

What was your argument to choose mocha over jasmine?

Peter Butkovic said...

@JoshuaMuheim as I'm quite new to both of these, no real arguments here

c_world_poster said...

Actually, the opposite is true. Each DB has its own special sql and data types. That is what this article is describing. It is not describing Hibernate issues.

I have hand written SQL in All the dbs you have listed and then some. There are differences if you want to do anything but simple SQL.

If you don't use something to abstract the differences, then it will be "hard" to switch. (Try generating DDL).

Peter Butkovic said...

bug is fixed, just go for the p6spy 2.0.1

Lukas Eder said...

True, if you hand-write your (string-based) "database-agnostic" SQL, you're about to set sails to the edge of the world ;-)


DDL is still (and will always be) something very very vendor-specific. With DML, however, you're right. HQL has abstracted things quite well, although to the price of a very reduced feature-set.

c_world_poster said...

HQL is reduced, but not "very reduced". Using Tables as your model and eliminating POJOs increases your code overhead. I do some very complicated things in HQL. And if i really need to, i can drop to SQL. I have only had to one or two times in the years I have used it. (to include NHibernate).


There are trade offs in most things. When we like something or are "marketing" it, we tend to only focus on the Cons of the other product. I have been reading your blog posts and I see a lot of that. JOOQ seems like a good tool to have in the bag, but don't ignore the Cons. Or the Pros of the other product.

Lukas Eder said...

Fair enough. We're not ignoring the pros of HQL, but in terms of SQL:2011 standards, I still think it is "very reduced". As in: Missing MERGE, window functions, grouping sets, derived column lists, common table expressions, row value expressions, sophisticated predicates, table-valued functions, etc. etc.

That doesn't mean it's bad though - and I think we stress that often enough. HQL responds to entirely other needs than SQL.

Sibi said...

Saved my life, thanks. Had exactly this issue in KDE with the latest KUbuntu 14.04.

sebasjm said...

and this is how a simple post can save the day of many. thanks

mindgrep said...

Thanks for the post. I was able to identify the culprits in my case using the command you posted. In my case I got something like:

2 /proc/20759/fd/anon_inode:inotify
1 /proc/3202/fd/anon_inode:inotify
1 /proc/3113/fd/anon_inode:inotify....

...


I could then identify the processes using the PIDs from the paths under /proc above, namely 20759, 3202 etc.


In my case the biggest offender turned out to be google chrome.

Ted C. Howard said...

Thank you very much for posting this. Missing the Ctrl+F6 shortcut in Eclipse has been the bane of my existence for several months now. I finally got fed up and looked for a solution, and Google led me here.

Carlos Pruitt said...

A wonderful golden nugget! Thank you.

gruzilla said...

thanks a lot man, you saved my day... i dont understand how somebody comes up with the idea of setting ctrl+space as "switch to next keyboard layout" - maybe inspired by touch keyboards??

i have no name said...

ctrl + space is a shortcut in midnight commander to get the size of the directory contents, i use it alot.

i was one step away to throw xfce away because of this,
until i discovered your solution.

Mikkel said...

Thanks, I also solved it by deleting the keyboard shortcut from "IBus preferences" (which is shown as a keyboard with a globe to illustrate that it lets you select input language.

HappyMinds! Software said...

Very very very thanks!!

David Wonnacott said...

THANK YOU. Control-space seems to be hardwired into by brain from decades of emacs use, and I kept copy-paste'ing the wrong text before I could stop myself and use a different keystroke.


The only thing I had to figure out was how to get to iBus prefs. On my xubuntu system, I found it listed with the title "keyboard input methods" in the XFCE Settings Manager.