From: MON KEY <monkey@sandpframing.com>
To: emacs-devel@gnu.org
Subject: Re: longlines-mode and visual-line-mode
Date: Tue, 2 Jun 2009 23:09:57 -0400 [thread overview]
Message-ID: <d2afcfda0906022009ha86fd69h8b4f400c95554636@mail.gmail.com> (raw)
> Anyway, I believe the following is useful but still missing in v-l-m, a
> variable to control the width, i.e. if it is positive integer, it
> controls the length of the line, otherwise it is the distance from the
> window edge to the right-most char of the line.
Realized this evening where Mr. Yidong may be looking to -> grapheme-clusters.
Now that the underlying Emacs encoding is "..to Unicode and Beyond"
this would seem a likely approach esp. coupled with the users
language-environment settings.
Fancy that...
(defun my-grapheme-fuzz-factor-pref ()
(if (and (member
(cdr (assoc 'major-mode (buffer-local-variables)))
'(language-o-choice-mode
language-o-plenty-mode
emacs-rdf-graph-navigator-mode))
(and (assoc 'syntax-table text-property-default-nonsticky)
(cdr (assoc 'syntax-table text-property-default-nonsticky))))
(setq right-most-grapheme-avoidance 3)))
(set (make-local-variable 'grapheme-wrap-fuzz-factor) nil)))
(add-hook 'buffer-grapheme-wrap-fuzziness-hook 'my-grapheme-fuzz-factor-pref)
Or, for the bidi bound - test for a front-skicky instead in
`my-grapheme-fuzz-factor-pref' and
(setq left-most-grapheme-avoidance 3) instead :)
next reply other threads:[~2009-06-03 3:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 3:09 MON KEY [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-01 5:14 longlines-mode and visual-line-mode MON KEY
2009-06-01 9:55 ` tomas
2009-06-01 10:01 ` Lennart Borgman
2009-06-01 13:27 ` Leo
2009-06-01 0:53 MON KEY
2009-06-01 2:27 ` Leo
2009-06-01 14:08 ` Stefan Monnier
2009-05-31 16:05 Leo
2009-05-31 16:26 ` Deniz Dogan
2009-05-31 17:03 ` Miles Bader
2009-05-31 17:11 ` Leo
2009-05-31 17:17 ` Deniz Dogan
2009-05-31 17:21 ` David Reitter
2009-05-31 17:55 ` Leo
2009-05-31 21:21 ` Chong Yidong
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2afcfda0906022009ha86fd69h8b4f400c95554636@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=emacs-devel@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.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).