ping <[email protected]> a écrit:
> I've recently started my blogging via jekyll and immediately feel 
> addicted into it.
> but it looks not quite feel a vim way .
> I have to
> 1) :!rake post title="my title"
> 2) go find that generated post template in _post dir and open it
> 3) and edit

Something like this, perhaps:

  com! -nargs=1 NewPost execute '!rake post title=<q-args>' | e YOUR_FILE

Of course I don't know how you can identify YOUR_FILE.

> 4) :!git .... or use fugitive git plugin to get it published

Same way: create a :command.

> is there a good way to automate at least step 1 and 4 ?
> 
> and there is one thing specifically I really wanted to archive for quite 
> a while:
> 
> I usually work in some a long , but organized text file. and sometime I 
> really want to quickly put
> some really good texts that I'm editing/viewing into a blog post and 
> publish it.
> currently I have to:
> 1) visual select the texts that i want to post
> 2) copy them into a new buffer
> 3) add some yaml front matter stuff like the following:
> 
>   ---
>   layout: post
>   title: "github/jeklly notes"
>   description: ""
>   category:
>   tags: []
>   ---
>   {% include JB/setup %}
> 
> 4) save them as a md file into the _post folder
> 
> what is the best vim-way to automate these?

I'd say, again, write a command/function, e.g.:

function! s:Post (fname) range
  exe a:firstline . "," . a:lastline . "yank"
  exe "tabnew /path/to/your/dir/" . a:fname . ".md"
  call append(0, ["Some", "lines", "of", "text."])
  normal p
endfunction

com! -nargs=1 Post call s:Post(<q-args>)

Best,
Paul

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to