Excerpts from Jean-Philippe Bernardy's message of Tue Mar 31 21:11:00 +0200 
2009:
> 
> On Tue, Mar 31, 2009 at 8:56 PM,  <codesite-nore...@google.com> wrote:
> >
> >
> > Comment #1 on issue 258 by nicolas.pouillard: make the buffer data
> > structure store chars
> > http://code.google.com/p/yi-editor/issues/detail?id=258
> >
> > This could make some byte based commands (notably in Vim mode) hard to
> > implement, though
> >
> 
> I'd say impossible, since the encoding will be lost. Would that be a problem?
> Basically the view is that we have a text (character) editor, not a byte 
> editor.

Although I don't want to develop a separate byte editor neither.

I guess that we will be able to select the encoding in which we want to edit
the file, and here we will be able to open without encoding.

If this is the case one just have to list features about bytes and classify
them.

While looking at the Vim manual about the 'go' command:

  :[range]go[to] [count]                                  *:go* *:goto* *go*
  [count]go               Go to {count} byte in the buffer.  Default [count] is
                          one, start of the file.  When giving [range], the
                          last number in it used as the byte count.  End-of-line
                          characters are counted depending on the current
                          'fileformat' setting.
                          {not in Vi}
                          {not available when compiled without the
                          |+byte_offset| feature}

Notice the mentioned "byte_offset" feature :)

Vim also have a feature to look at the underlying character representation,
which is extremely valuable when dealing with encodings problems accents and 
the like.

If someone else have ideas about features that could break, please add it to 
this topic.

Cheers,

-- 
Nicolas Pouillard

--~--~---------~--~----~------------~-------~--~----~
Yi development mailing list
yi-devel@googlegroups.com
http://groups.google.com/group/yi-devel
-~----------~----~----~----~------~----~------~--~---

Reply via email to