From: SAKURAI Masashi <m.sakurai@kiwanami.net>
To: rasmus@gmx.us
Cc: emacs-orgmode@gnu.org
Subject: Re: [calfw] Better use of space
Date: Thu, 08 Sep 2011 10:50:53 +0900 [thread overview]
Message-ID: <20110908015054.16A9513C550@vps1.kiwanami.net> (raw)
In-Reply-To: <87k49ksqfj.fsf@gmail.com>
Thanks for your comment!
At Wed, 07 Sep 2011 10:32:48 +0200,
Rasmus wrote:
> :
>
> Emacs has several built-in word wrapping mechanisms. See
> Options → Line Wrapping in this buffer
> for an overview. My preferred method is Word Wrap. Whether this can
> easily be utilized by calfw I don't know.
Yes. I seem this word wrapping algorithm is a simple one (it may be
the same as 'fill-region'), which is shown at the Wikipedia. To fill
out the narrow space efficiently, I think hyphenation is needed.
I will continue to search the better algorithm.
> > If you have a time, will you check it out?
> > I would like to hear feeling from the not East Asians users,
> > using line breaking without no smart word-wrapping and hyphenation.
>
> It works okay. The problem is not so much the line breaking as the lack
> of appropriately segregating entries.
>
> The following view is decent, and word wrap certainly improves
> the ease of obtaining information:
> http://ompldr.org/vYThpOQ
>
> On the other hand information is not easily obtained from a week with
> lots of scheduled class from a single file:
> http://ompldr.org/vYThpYQ
>
> - An easy solution might be do add a `\n' but this might not always be
> desirable.
> - Events could also be separated by lines.
> - Different shades might also be a possibility. Here is a screenshot of
> my Gnus group buffer which is striped.
> http://ompldr.org/vYThpZQ
I think the current look needs to improve in the case of many
schedules too.
Many schedule items, like Japanese TV programs guides...
https://twitter.com/#!/kiwanami/status/110721726375145472/photo/1/large
I'm going to try some improvement, such as inserting a horizontal
line, applying different face on the first lines and shading like gnus
group buffer.
I will inform here again.
Thank you,
--
SAKURAI, Masashi (family, given)
m.sakurai@kiwanami.net
prev parent reply other threads:[~2011-09-08 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 8:57 [calfw] Better use of space Rasmus
2011-07-22 7:03 ` SAKURAI Masashi
2011-07-22 9:12 ` Rasmus
2011-07-25 3:41 ` SAKURAI Masashi
2011-09-06 2:11 ` SAKURAI Masashi
2011-09-07 8:32 ` Rasmus
2011-09-08 1:50 ` SAKURAI Masashi [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
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=20110908015054.16A9513C550@vps1.kiwanami.net \
--to=m.sakurai@kiwanami.net \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).