emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: zeltak <zeltak@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [Out-of-Thread] Re: [RFC] Org syntax (draft)
Date: Mon, 18 Mar 2013 09:33:14 -0400	[thread overview]
Message-ID: <CAN2HUWgigYP4L0SSCwjDfbPF-SQdi7AQPkcg5CSeQ5cNPc2r=g@mail.gmail.com> (raw)
In-Reply-To: <6449B53A-997D-411D-8E13-AAFAE6D81397@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3436 bytes --]

Dear Carsten,

Thank you for your quick reply. Let me start by first thanking you for your
great work on orgmode, I only recently discovered it (someone referred me
to your great talk on youtube) and it made me have the courage to start
learning emacs and use orgmode.

I  (actually me and several colleagues here at the school of public health
at Harvard) have been using for the past 4 years a note taking app called
notecase pro (http://www.notecasepro.com/) which is nice but not FLOSS and
lacking in other areas. I am a post doc who takes alot of notes (30-40)
daily which include images and color markings.

colors are especially important to us since we use them to
mark different commands, research areas, paths, comments and warning so
that we have a clear easy to remember color visual clue. We use 15-20 color
fg/bg commands. An example note could look like this:

http://i.imgur.com/Ncq6ozs.png

i am a complete new orgmode user but i am so impressed and overblown with
the features and definitely want to transition to use it full time and also
convince my colleagues to do so as well. with the help of the #irc channel
i was able to use the customizing features for the emphasize symbols to
achieve color support . the config now looks like this:

 '(org-emphasis-alist (quote (("@" (:foreground "#B40000" :background
"#FFDDDD" :weight bold) "" "") ("$" (:foreground "#FF0000") "" "") ("*"
bold "<b>" "</b>") ("/" italic "<i>" "</i>") ("_" underline "<span
style=\"text-decoration:underline;\">" "</span>") ("=" org-code "<code>"
"</code>" verbatim) ("~" org-verbatim "<code>" "</code>" verbatim) ("+"
(:strike-through t) "<del>" "</del>"))))

That would have worked for me but i understood that there are plans to
actually disable these customization's in the next version to allow
better portability.

If its not to hard It would be great to have a method similar to the
customizable
emphasis that lets a user define custom colors of FG/BG for inline viewing.
I am less concerned about exporting since at least for me i plan to do all
the editing/viewing inline inside emacs (though it would be nice of course
to be able to use it with mobile org and/or other mobile solutions for when
we do field work).

I will hold on with starting with the mammoth task of converting my
Notecase notes into orgmode until the issues is resolved, i assume i should
follow the mailing list to check on this?

Sorry for the long email and thank you so much again for all your work,
its truly fantastic

Z.












On Mon, Mar 18, 2013 at 2:08 AM, Carsten Dominik
<carsten.dominik@gmail.com>wrote:

> Hi Z,
>
> can you show an example on how you use it?  Maybe we can find a better
> way.  Nicolas is right that portability is compromised by customizable
> emphasis.
>
> - Carsten
>
>
>
> On 18.3.2013, at 00:02, zeltak <zeltak@gmail.com> wrote:
>
> > Hi all
> >
> > i just finished a great conversation on #org-mode with some great
> people. they told me about this thread and the planned changes that may or
> may not occur to the syntax and id like to just raise the newbee
> perspective.
> >
> > I find the ability to add custom emphasise with custom faces invaluable.
> i find it very easy to add and very useful for me since i use ALOT of color
> highlights in my academic work.
> >
> > i really hope that there is some way to leave the current mphasise with
> custom faces options as is
> >
> >
> > thx alot guys
> >
> > Z
>
>

[-- Attachment #2: Type: text/html, Size: 5533 bytes --]

  parent reply	other threads:[~2013-03-18 13:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 23:02 [Out-of-Thread] Re: [RFC] Org syntax (draft) zeltak
2013-03-18  6:08 ` Carsten Dominik
2013-03-18 10:48   ` Thorsten Jolitz
2013-03-18 13:33   ` zeltak [this message]
2013-03-18 15:21     ` W. Greenhouse
2013-03-18 16:05       ` Marcin Borkowski
2013-03-18 19:19       ` Carsten Dominik
2013-03-18 21:24         ` Rasmus
2013-03-19  3:47         ` Aaron Ecay
2013-03-19  9:49         ` Nicolas Richard
2013-03-21 21:36         ` Nicolas Goaziou
2013-04-12  6:23           ` Bastien
2013-04-12  6:23         ` Bastien
2013-03-19  4:07       ` Samuel Wales
  -- strict thread matches above, loose matches on Subject: below --
2013-03-20 17:47 zeltak
2013-03-07 20:37 Nicolas Goaziou
2013-03-09 23:16 ` Achim Gratz
2013-03-09 23:49   ` Nicolas Goaziou
2013-03-10  4:35     ` Jambunathan K
2013-03-10  7:08       ` Nicolas Goaziou
2013-03-10 10:14         ` Bastien
2013-03-10 15:44           ` Jambunathan K
2013-03-14 16:58             ` Eric S Fraga
2013-03-14 18:26               ` Jambunathan K
2013-03-14 18:51                 ` David Engster
2013-03-14 19:03                   ` [Out-of-Thread] " Jambunathan K
2013-03-14 19:15                     ` David Engster
2013-03-14 19:23                       ` Jambunathan K
2013-03-14 19:29                         ` David Engster
2013-03-14 19:52                           ` Jambunathan K

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to='CAN2HUWgigYP4L0SSCwjDfbPF-SQdi7AQPkcg5CSeQ5cNPc2r=g@mail.gmail.com' \
    --to=zeltak@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).