public inbox for howm-eng@lists.osdn.me
 help / color / mirror / Atom feed
From: tongconsulting at gmail.com (Jin Tong)
Subject: [Howm-eng 18] Re: Question/Feature Requests
Date: Fri, 18 Nov 2005 21:15:48 -0500	[thread overview]
Message-ID: <cab33e5b0511181815t751ac45awe143e77a70a04194@mail.gmail.com> (raw)
In-Reply-To: <m3y83m6m2r.wl@telperion.i>

I agree with your approach (i.e. markup and formatting is not a
concern of howm mode). But your quick example works well too, thanks.

org+howm (and outline+howm) works fine, too.

Thanks again!

On 11/18/05, khi at users.sourceforge.jp <khi at users.sourceforge.jp> wrote:
>
> Here is an example.
>
> ;; _underline_ and *emphasize*
> (setq howm-user-font-lock-keywords
>       '(("\\(^\\|\\s-\\)\\(_\\w+?_\\)\\(\\s-\\|$\\)"
>          2 'underline prepend)
>         ("\\(^\\|\\s-\\)\\([*]\\w+?[*]\\)\\(\\s-\\|$\\)"
>          2 'font-lock-comment-face prepend)))
>
> Ideally, I believe that howm itself should not offer any
> formatting/markup rules, so that you can combine howm with your
> favorite writing style.  It's the first motivation why I'm not
> satisfied with emacs-wiki and I began to make my own tool.
>
> Since howm-mode is a minor-mode, it can be used with any other modes
> theoretically.  Indeed, I personally use rd-mode, rd-mode-plus, and
> outline-minor-mode for markup and outline support, together with howm.
>   http://lists.sourceforge.jp/mailman/archives/howm-eng/2005/000014.html
>
> Other combinations are not tested sufficiently.  If you have any
> trouble with outline+howm or org+howm, please let me know.
>
> --
> khi at users.sourceforge.jp
> _______________________________________________
> Howm-eng mailing list
> Howm-eng at lists.sourceforge.jp
> http://lists.sourceforge.jp/mailman/listinfo/howm-eng
>


      reply	other threads:[~2005-11-19  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 14:57 [Howm-eng 17] " khi
2005-11-19  2:15 ` tongconsulting [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cab33e5b0511181815t751ac45awe143e77a70a04194@mail.gmail.com \
    --to=howm-eng@lists.osdn.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).