Emacs.app is the name of the bundle that contains the app. On Mac OS
X Finder and throughout the graphical interface the name appears as
"Emacs". Any build of emacs that is meant to be run from the Mac
graphical interface should be called "Emacs".
That seems right.
We're d
> The default build on mainline for Mac OS X is referred to as "Carbon" as
> distinct from the "X11" build. But it's still "Emacs", as would a build
> based on GNUStep compiled under Cocoa.
Before being integrated in the main code, the w32 code for Emacs was called
NTEmacs, and nowadays it's s
On Sep 22, 2005, at 2:03 AM, Steven Tamm wrote:
As for the unicode branch, the way that unicode font handling is done
on the Mac (ATSUI) is different from the old-style (Quickdraw) that is
used in the Carbon port.Quickdraw is based on MBTE and converting
it to unicode is hard. I've done
Sorry to jump in late,
Emacs.app is the name of the bundle that contains the app. On Mac OS
X Finder and throughout the graphical interface the name appears as
"Emacs". Any build of emacs that is meant to be run from the Mac
graphical interface should be called "Emacs".
Aqua = Name of th
"Emacs.app" is a good name. Mac users will recognize its relevance,
but it doesn't publicize Macintosh otherwise.
So let's use that.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Adrian Robert <[EMAIL PROTECTED]> writes:
> On Sep 15, 2005, at 9:00 AM, Richard M. Stallman wrote:
>
>> That's correct -- or actually the GNUstep "version" and the OS X
>> one
>> are the same code, with a few ifdefs here and there. The APIs
>> provided by GNUstep and Cocoa are almost
On Sep 15, 2005, at 9:00 AM, Richard M. Stallman wrote:
That's correct -- or actually the GNUstep "version" and the OS X
one
are the same code, with a few ifdefs here and there. The APIs
provided by GNUstep and Cocoa are almost identical (or at least
largely overlapping; pleas
"Chong Yidong" <[EMAIL PROTECTED]> writes:
> (2) Fix recognition of shell's `dirs' command.
I've just installed a fix for this problem.
--
Romain Francoise <[EMAIL PROTECTED]> | I just thought I'd go out
it's a miracle -- http://orebokech.com/ | with a little bit more style.
That's correct -- or actually the GNUstep "version" and the OS X one
are the same code, with a few ifdefs here and there. The APIs
provided by GNUstep and Cocoa are almost identical (or at least
largely overlapping; please see http://gnustep.org for more
explanation) T
Thanks for taking the time to explain the problem. I can definitely
reproduce this.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Chong Yidong <[EMAIL PROTECTED]> writes:
> What do you mean by "in some cases"? Is there a consistent way to
> reproduce this, i.e., step by step instructions for getting
> shell-resync-dirs confused?
1. Start a shell in Emacs: SHELL=bash emacs -Q -f shell
2. Make the shell echo: stty echo RET
3
> If someone would prefer some alternative (e.g., using 'arch' in some funky
> way), please let me know. I'm just assuming no one is going to want the
> Cocoa/GNUstep code anywhere near the main Emacs tree itself until it's
> quite stable.
As far as I'm concerned, I wouldn't mind seeing it added
On Sep 13, 2005, at 12:25 PM, Stefan Monnier wrote:
What I'm getting
at is, is it reasonable to port Emacs-on-Aqua to this branch now, or
should I stick with the to-be-22.1 code
If the unicode-2 branch would make your job much easier, I
think going
with the branch would be a perf
IIUC Adrian Robert works mainly on the GNUstep version, which is free and
runs on free systems.
He was talking about "Emacs for Aqua".
Isn't Aqua the name of a version of MacOS?
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.
> Sure. In a nutshell, the optional part of the regular expression
> sometimes doesn't match even when there is an echoed
> `shell-dirstack-query' command, so the command is considered to be the
> directory list. (The change we installed back in 2003 was to add this
> optional part.) Depending o
Emilio Lopes <[EMAIL PROTECTED]> writes:
> Maybe you could report your experience so far, so that others with the
> motivation need not to go all the process for themselves again.
Sure. In a nutshell, the optional part of the regular expression
sometimes doesn't match even when there is an echoe
Romain Francoise writes:
> "Chong Yidong" <[EMAIL PROTECTED]> writes:
>> (2) Fix recognition of shell's `dirs' command.
> I can reproduce it with bash and 'stty echo', or with zsh. We
> installed a change in 2003 that is supposed to fix the problem but
> doesn't work in all cases. I spent some
>> What I'm getting
>> at is, is it reasonable to port Emacs-on-Aqua to this branch now, or
>> should I stick with the to-be-22.1 code
> If the unicode-2 branch would make your job much easier, I think going
> with the branch would be a perfectly reasonable thing to do.
> To release this
1) When is the best estimate of when 22.1 will come out?
I would estimate two months. Of course, it could be longer.
2) Is 22.1 being released off its own branch (instead of the head),
No.
3) How much significant unicode-2-specific work remains before that
branch becomes el
Assuming that problem is really fixed, there are only five bugs left
in the list, of which three can be resolved quickly:
We also need people to finish checking the files of the manuals, and
finish updating the copyright years in just a couple of directories.
But overall you're right--prog
> What I'm getting
> at is, is it reasonable to port Emacs-on-Aqua to this branch now, or
> should I stick with the to-be-22.1 code
If the unicode-2 branch would make your job much easier, I think going
with the branch would be a perfectly reasonable thing to do.
To release th
On Sep 12, 2005, at 3:35 PM, Stefan Monnier wrote:
OTOH if the work can be expected to take in the order of a few
months only
(i.e. a large part of the work you've done on 20.7 can be reused
with little
or no changes), it would also make sense to start from the current
HEAD (to
be 22.1).
Nick Roberts <[EMAIL PROTECTED]> writes:
> > > That does beg the question as to why unicode-2 hasn't already been
> > > merged into HEAD given that, using timescales for Emacs 22, Emacs 23
> > > won't be released until about 2010.
> >
> > So that Emacs 22 will not get released only in 2010.
Thanks all for the info; I'll start examining the unicode-2 code..
-Adrian
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
* Nick Roberts (2005-09-13) writes:
> > > That does beg the question as to why unicode-2 hasn't already been
> > > merged into HEAD given that, using timescales for Emacs 22, Emacs 23
> > > won't be released until about 2010.
> >
> > So that Emacs 22 will not get released only in 2010.
>
> T
> > That does beg the question as to why unicode-2 hasn't already been
> > merged into HEAD given that, using timescales for Emacs 22, Emacs 23
> > won't be released until about 2010.
>
> So that Emacs 22 will not get released only in 2010.
The description Miles gave suggested that unicode-2
Nick Roberts <[EMAIL PROTECTED]> writes:
> Miles Bader writes:
> > I use unicode-2 as my "secondary" emacs, and it seems pretty stable,
> > more or less identical to the trunk.
>
> and
>
> > my impression is that
> > by-and-large, the unicode-2 branch is not
"Chong Yidong" <[EMAIL PROTECTED]> writes:
> (2) Fix recognition of shell's `dirs' command.
> I installed tcsh, turned on command echoing, and was unable to get the
> `dirs' command confused. Let's just close this, unless someone else
> is seeing the problem.
I can reproduce it with bash and 's
> From: Stefan Monnier <[EMAIL PROTECTED]>
> Date: Mon, 12 Sep 2005 17:37:13 -0400
> Cc: emacs-devel@gnu.org
>
> >> > 1) When is the best estimate of when 22.1 will come out?
> >> Not before 2006.
> > I hope it can be done faster than that!
>
> I hope so as well, but my best estimate is still "no
2005/9/13, Nick Roberts <[EMAIL PROTECTED]>:
> > my impression is that
> > by-and-large, the unicode-2 branch is not going to change
> > dramatically.
>
> That does beg the question as to why unicode-2 hasn't already been merged into
> HEAD given that, using
On 9/12/05, Chong Yidong <[EMAIL PROTECTED]> wrote:
> I hope it can be done faster than that!
I'll eat my Emacs reference card if 22.1 is out before *2007*. Yeah,
I've read the rest of the thread. I'll be delighted to be proven
wrong.
> (3) Emacs on Windows crashes on JPEG images from files in u
Miles Bader writes:
> I use unicode-2 as my "secondary" emacs, and it seems pretty stable,
> more or less identical to the trunk.
and
> my impression is that
> by-and-large, the unicode-2 branch is not going to change
> dramatically.
That does beg the que
2005/9/13, Adrian Robert <[EMAIL PROTECTED]>:
> And how stable / bug-free is unicode-2
> right now compared with the will-become-22.1 code?
I use unicode-2 as my "secondary" emacs, and it seems pretty stable,
more or less identical to the trunk. The main problems I've had seem
to mostly be relate
>> > 1) When is the best estimate of when 22.1 will come out?
>> Not before 2006.
> I hope it can be done faster than that!
I hope so as well, but my best estimate is still "not before 2006".
Stefan
___
Emacs-devel mailing list
Emacs-devel@gn
"Chong Yidong" <[EMAIL PROTECTED]> writes:
> Can we start the release process once these five bugs are resolved, or
> is there any more reason to delay?
Starting the release process means to start the pre-test.
IMO, solving the remaining problems don't need to postpone that,
but Richard has the
"Chong Yidong" <[EMAIL PROTECTED]> writes:
> Stefan Monnier <[EMAIL PROTECTED]> writes:
>
>> > 1) When is the best estimate of when 22.1 will come out?
>>
>> Not before 2006.
>
> I hope it can be done faster than that!
[...]
> Can we start the release process once these five bugs are resolved,
>
Stefan Monnier <[EMAIL PROTECTED]> writes:
> > 1) When is the best estimate of when 22.1 will come out?
>
> Not before 2006.
I hope it can be done faster than that!
Looking through FOR-RELEASE, the only major bug left to fix is the
compact_small_strings/string_free_list problem -- which may have
> 1) When is the best estimate of when 22.1 will come out?
Not before 2006.
> My second question concerns the unicode-2 branch of CVS. As I understand
I don't know much about Aqua/Cocoa/Carbon, and more specifically I don't
know how different are Cocoa and Carbon, so I don't know who much of t
Hi,
I'm maintaining the Emacs-on-Aqua GNUstep / OS X port, currently
based on emacs 20.7 (http://emacs-on-aqua.sf.net/). I want to update
this to a more recent version but would ideally like to do so against
a stabilized / released version of GNU emacs -- just so I know that
bugs are my
39 matches
Mail list logo
