On 25 February 2011 11:05, Corinna Vinschen wrote:
> On Feb 25 09:05, Thomas Wolff wrote:
>> For cygwin, it might be useful (although not standard) for wcwidth
>> to consider whether it's running in a cygwin console or a terminal,
>> so e.g. wcwidth (0x8080) should return 2 in mintty but 1 in a cyg
On Fri, Feb 25, 2011 at 13:46, Bengt Larsson wrote:
> Bengt Larsson wrote:
>>Kenneth Wolcott wrote:
>sigh, no ^X d (aka dired mode) by default !
True. I never use it. I kind of philosophically disagree with it.
>>>
>>> Strange, as "dired" is one of the most important pieces of emacs
Bengt Larsson wrote:
>Kenneth Wolcott wrote:
sigh, no ^X d (aka dired mode) by default !
>>>
>>> True. I never use it. I kind of philosophically disagree with it.
>>
>> Strange, as "dired" is one of the most important pieces of emacs and
>>when one says "emacs" and then says "but this version
Kenneth Wolcott wrote:
>>>sigh, no ^X d (aka dired mode) by default !
>>
>> True. I never use it. I kind of philosophically disagree with it.
>
> Strange, as "dired" is one of the most important pieces of emacs and
>when one says "emacs" and then says "but this version doesn't have
>'dired'", the
On Feb 25 09:05, Thomas Wolff wrote:
> Am 24.02.2011 09:56, schrieb Corinna Vinschen:
> >When on Cygwin, you might better use Cygwin's(*) wcwidth function. It's
> >based on the same code from Markus Kuhn, but it interacts with the
> >setlocale function to make sure that the width returned for the
Am 24.02.2011 09:56, schrieb Corinna Vinschen:
When on Cygwin, you might better use Cygwin's(*) wcwidth function. It's
based on the same code from Markus Kuhn, but it interacts with the
setlocale function to make sure that the width returned for the CJK
ambiguous width characters makes sense in
One comment in-line...
On Thu, Feb 24, 2011 at 22:47, Bengt Larsson wrote:
> Cyrille Lefevre wrote:
>
> Thanks for your informed criticism. But I haven't suggested it should be
> delivered with Cygwin.
>
>>make install should copy mg to /bin instead of /docs/Command,
>
> Yup
>
>>copy
>>documentat
Cyrille Lefevre wrote:
>
>forgot about make install :
Again Super-helpful. Thanks.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-si
Cyrille Lefevre wrote:
Thanks for your informed criticism. But I haven't suggested it should be
delivered with Cygwin.
>make install should copy mg to /bin instead of /docs/Command,
Yup
>copy
>documentation files in /usr/share/doc/mg3a and samples (dot files)
>in /us/share/doc/mg3a/examples
forgot about make install :
install: strip installbin installdoc
PREFIX=/usr
#PREFIX=/usr/local
BINDIR=${PREFIX}/bin
DOCDIR=${PREFIX}/share/doc/mg3a
DOCFILES=README README.misc README.programmer README.reference \
orig/mgprog.doc orig/README orig/tutorial
SAMPDIR=${DOCDIR}/examples
SAMF
Le 24/02/2011 19:50, Bengt Larsson a écrit :
Utf-8 and a number of 8-bit charsets, actually. I'm getting rather
annoyed that people judge the program without looking at it. And it does
use nl_langinfo(CODESET).
make install should copy mg to /bin instead of /docs/Command, copy
documentation
Andy Koppe wrote:
>On 24 February 2011 11:14, Corinna Vinschen wrote:
>> On Feb 24 11:56, Bengt Larsson wrote:
>>> I don't use surrogates. I only use UTF-8 and UTF-32.
>
>... which of course means that you don't support anything but UTF-8
>and ASCII locales. Can't argue with that, but you might wan
On 02/24/2011 04:50 AM, Corinna Vinschen wrote:
> On Feb 24 12:19, Bengt Larsson wrote:
>> Bengt Larsson wrote:
>>> I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's
>>> wcwidth may be worth thinking about. I suppose it will be consistent
>>> with mintty that way; otherwise no
On 24 February 2011 11:14, Corinna Vinschen wrote:
> On Feb 24 11:56, Bengt Larsson wrote:
>> I don't use surrogates. I only use UTF-8 and UTF-32.
... which of course means that you don't support anything but UTF-8
and ASCII locales. Can't argue with that, but you might want to use
nl_langinfo(COD
On Feb 24 12:40, Bengt Larsson wrote:
> Corinna Vinschen wrote:
> >> Using wcswidth isn't very useful in the editor because it has special
> >> requirements, like showing control characters with ^C.
> >
> >Well, it's not really such a big problem to special case wide char
> >control values and just
On Feb 24 12:19, Bengt Larsson wrote:
> Bengt Larsson wrote:
> >I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's
> >wcwidth may be worth thinking about. I suppose it will be consistent
> >with mintty that way; otherwise not?
>
> And: is wcwidth always available in modern Uni
Corinna Vinschen wrote:
>> Using wcswidth isn't very useful in the editor because it has special
>> requirements, like showing control characters with ^C.
>
>Well, it's not really such a big problem to special case wide char
>control values and just call wcswidth otherwise...
Oh I see. wcwidth tak
Bengt Larsson wrote:
>I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's
>wcwidth may be worth thinking about. I suppose it will be consistent
>with mintty that way; otherwise not?
And: is wcwidth always available in modern Unices? How do you find out
these things? I mean prac
On Feb 24 11:56, Bengt Larsson wrote:
> Corinna Vinschen wrote:
> >Just a hint:
> >
> >When on Cygwin, you might better use Cygwin's(*) wcwidth function. It's
> >based on the same code from Markus Kuhn, but it interacts with the
> >setlocale function to make sure that the width returned for the CJ
Corinna Vinschen wrote:
>Just a hint:
>
>When on Cygwin, you might better use Cygwin's(*) wcwidth function. It's
>based on the same code from Markus Kuhn, but it interacts with the
>setlocale function to make sure that the width returned for the CJK
>ambiguous width characters makes sense in the g
On Feb 23 20:36, Bengt Larsson wrote:
> Andrew Schulman wrote:
> >> Why not ITP it as an official package?
> >
> >It will need a license. Right now there's no license information anywhere
> >in the tarball AFAICT.
> >
> >Is the code in Mg3a taken from Emacs? If so, you need to include the GPL
> >
Andrew Schulman wrote:
>> Why not ITP it as an official package?
>
>It will need a license. Right now there's no license information anywhere
>in the tarball AFAICT.
>
>Is the code in Mg3a taken from Emacs? If so, you need to include the GPL
>in your tarball.
No, it was taken from Mg2a, which wa
> Bengt Larsson sent the following at Wednesday, February 23, 2011 3:58 AM
> >
> >As I mentioned in an earlier message I have been developing UTF-8
> >support for an editor, Mg2a. I chose to call it Mg3a.
> >
> >You can fetch it here: http://www.bengtl.net/files/mg3a/
> >
> >Or directly here: http:
Bengt Larsson sent the following at Wednesday, February 23, 2011 3:58 AM
>
>As I mentioned in an earlier message I have been developing UTF-8
>support for an editor, Mg2a. I chose to call it Mg3a.
>
>You can fetch it here: http://www.bengtl.net/files/mg3a/
>
>Or directly here: http://www.bengtl.net
Corinna Vinschen wrote:
>On Feb 23 10:11, Bengt Larsson wrote:
>> If you are on Cygwin, Mg defaults to CRLF line endings. You may want
>> to set them to LF by putting this in a file .mg in your home
>> directory:
>>
>> (set-default-mode "lf")
>
>I'm not an Emacs user, but IMO LF should be the de
On Feb 23 10:11, Bengt Larsson wrote:
> Bengt Larsson wrote:
> >As I mentioned in an earlier message I have been developing UTF-8
> >support for an editor, Mg2a. I chose to call it Mg3a.
>
> The README:
>
> This is Mg, formerly Mg2a, formerly MicroGnuEmacs. It was extended by
> Bengt
Bengt Larsson wrote:
>As I mentioned in an earlier message I have been developing UTF-8
>support for an editor, Mg2a. I chose to call it Mg3a.
The README:
This is Mg, formerly Mg2a, formerly MicroGnuEmacs. It was extended by
Bengt Larsson to deal with CRLF/LF and UTF-8, plus some othe
As I mentioned in an earlier message I have been developing UTF-8
support for an editor, Mg2a. I chose to call it Mg3a.
You can fetch it here: http://www.bengtl.net/files/mg3a/
Or directly here: http://www.bengtl.net/files/mg3a/mg3a.110223.tar.gz
Just extract and compile. You can use it with onl
28 matches
Mail list logo
