To quote another one’s words, one can paraphrase the words. For some
reason(s), (Perhaps being too lazy, or want to accurately reflect
another one’s words.) one would like to directly quote what another
one has said.
To show the difference in $\rm \LaTeX$, I’ve made
a PDF file a year ago. It’s now on Google Docs.
I created the above PDF document using quote.tex.
For many computer users who aren’t familiar with $\rm \LaTeX$’s
syntax but HTML’s, they should find Markdown easy to write, and
pandoc easy to use.
Note: This post won’t make sense here. Refer to the
original post.
Note: I can now figure out a way to work with both UltraBlog and
WordPress.com’s built-in online code highlighter. See my
newer post for details.
Markdown is easy to write. However, writing code with code
tag (surrounded with []) using UltraBlog in Vim doesn’t work. In
order to post some code, one needs to
use 3 backticks. (I’ve found a way to use the
built-in SyntaxHighlighter now because I’ve realised that a blank line
in Markdown will be changed to a <p> tag in HTML. Thus, don’t put
any blank lines right above and below the the <code> tags.)
There’s some shortcomings of the above method. If you need to copy a
list of source code, you’ll need to browse the source code, provided
that the “gutter” option of the code list is “true”,
which is the default.
Moreover, if you include source code that consists of <angled
blocks> in a blog post written in Markdown using the UltraBlog
plugin, then the angled block may be interpreted as an HTML tag
element, such as the statement #include <iostream> in a C++ program.
More importantly, I’ve found out that this apporachdoesn’t work with UltraBlog.The above code list verifies
this assertion.
Figure 1: This is a screenshot of the “code list” in
UltraBlog.vim. Markdown quick reference suggests the
use of 3 backticks.
Figure 2: The above figure shows how the source code for the
“code list” (in lines 12–15 in UltraBlog.vim, see Figure 1) is
interpreted.
Before including the autocommand group, I’d write about the reason of
using it.
In my post titled Links to Good Posts, I’ve included some
custom autocompletion keyboard mappings for the automatic completion
of {}, [] and () blocks in my VIMRC file.
Last Thursday, I extended them to blocks enclosed by single or double
quotes.
I suspect that after I write the blog with UltraBlog in Vim and
editing the contents with the online editor, the changes done using
the online editor will be lost. (Typed with UltraBlog.vim in Vim.)
As a supporter of the GNU Project, I am not so happy to use
DISLIN, which comes with an EULA, but I don’t have time to find
out another alternative to the plotting library suggested by Prof.
Yevick in a book.1
This is what I’ve longed for. What makes it even better is that it’s a
website from a domain that ends in .gov, making it a reliable source
of information.
Having a good naming convention can greatly reduce the number of
syntax errors in the source code and improve its readability.
For what you can do using Google Form, you can refer to those online
forms that are created by Google.
The focus of this post is what you shouldn’t do while using online
forms that are accessible to the public, like Google Forms and other
platforms that enable users to easily create questionnaire.
I tried finding a way to blog using Vim, and blogger.vim is what
I’ve found. I’ve tried this plugin but it doesn’t work for my
computer. Without Vim, writing code is painful for me. Read the
authors’ last Blogger post, which was, ironically, about his switch
to WordPress, I followed his footstep.1
Note: For posts about online syntax highlighting and Mathjax on
Blogger, they won’t make sense here, so refer to
my original blog if necessary.