On Sat, Oct 04, 2014 at 02:10:02PM -0400, Matthias Clasen wrote:
> My main motiviation is that 'we follow TR29' is much better in terms
> of documenting it, testing it and diagnosing bugs in than 'do what vim
> does'.
That would work if TR29 specifies clearly the different word boundaries
to use f
On Sat, Oct 4, 2014 at 1:52 PM, Paul Davis wrote:
>> But the Vim word boundaries improve the behavior also for normal text,
>> not just code. Vim can be used to write mails and documents.
>
>
> this is none of my business, but it seems fairly clear to me what matthias
> wants:
>
> step 1: create
On Sat, Oct 4, 2014 at 1:48 PM, Sébastien Wilmet wrote:
> On Sat, Oct 04, 2014 at 12:30:43PM -0400, Matthias Clasen wrote:
>
> > For tayloring the text segmentation behavior for special situations,
> > such as code instead of natural language, a vfunc is the right
> > approach.
> >
> > Does that
On Sat, Oct 04, 2014 at 12:30:43PM -0400, Matthias Clasen wrote:
> I mean that it is the right default behavior to follow Unicode TR 29.
If we want to follow Unicode TR 29, then we should use the
is_word_boundary PangoLogAttr attribute, see:
https://bugzilla.gnome.org/show_bug.cgi?id=530405
As I
On Sat, Oct 4, 2014 at 8:24 AM, Sébastien Wilmet wrote:
> On Fri, Oct 03, 2014 at 10:25:36PM -0400, Matthias Clasen wrote:
>> I think I want the default in GtkTextView/Pango to stay basically
>> Unicode. So the vfunc may be needed sooner if you want to have
>> vim-like behaviour in GtkSourceView.
On Fri, Oct 03, 2014 at 10:25:36PM -0400, Matthias Clasen wrote:
> I think I want the default in GtkTextView/Pango to stay basically
> Unicode. So the vfunc may be needed sooner if you want to have
> vim-like behaviour in GtkSourceView.
What do you mean by basically Unicode?
The problems in GTK+:
