all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Károly Lo\"rentey" <karoly@lorentey.hu>
To: emacs-devel@gnu.org
Subject: Re: multi-tty branch created
Date: Wed, 16 May 2007 15:24:45 +0200	[thread overview]
Message-ID: <f2f0n2$dbd$1@sea.gmane.org> (raw)
In-Reply-To: <85646wpuqn.fsf@lola.goethe.zz>


[-- Attachment #1.1: Type: text/plain, Size: 2148 bytes --]

David Kastrup wrote:
> I've checked it out, compiled it, not yet used it.  README.multi-tty
> does not yet reflect the availability on Savannah.

I updated it a little.

> Is the GTK+ situation as described in there?

No, it has much improved.  AFAIK GTK still doesn't fully support
multiple displays, but the remaining bugs are mostly memory leaks, not
crashes.

> One thing that is mentioned that calling emacsclient from a different
> user will not work.  I think that this is really a non-issue since
> file accessibility from a different user would also be different and
> there is no really useful strategy short of using tramp for getting
> this to work.

I agree with your reasoning but the item is about something slightly
different:

	Login: fred
	Password:
	fred$ emacs
		M-x server-start

Meanwhile, in another session:

	Login: barney
	Password:
	barney$ su fred
	Password:
	fred$ emacsclient -t
	(Fails due to Emacs not being able to open the tty device.)

The use case: fred sits down before barney's console to show him
something under his own account.

> emacsclient operation in multitty is different as compared to
> previously.  So people can't avoid multitty completely, meaning that
> we can't bluntly state "situation can't be worse than previously, no
> regression" but need to evaluate multitty somewhat more closely before
> finding it suited for trunk, even if the compilation problems on
> DOS/Windows/Mac have been tackled.

Hold your horses.  There is always "emacsclient --current-frame" to
prevent emacsclient from creating a new terminal.  This retains much of
the functionality of the original emacsclient, including, I believe,
things like C-#, and does not use multi-tty features.

I hope most people would agree that the new emacsclient features are a
definite improvement.

> The precondition for trunk in my opinion would be that it does not
> impede workability for those people who are working on different parts
> of Emacs.

Keep in mind that improving emacsclient behaviour is one of the primary
results of the multi-tty branch.

-- 
Karoly


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  parent reply	other threads:[~2007-05-16 13:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 13:31 multi-tty branch created Miles Bader
2007-05-13 14:50 ` David Kastrup
2007-05-13 16:12   ` Miles Bader
2007-05-13 16:14     ` David Kastrup
2007-05-13 16:13   ` David Kastrup
2007-05-13 19:28     ` Robert J. Chassell
2007-05-16 13:24     ` Károly Lo"rentey [this message]
2007-05-16 13:46       ` Juanma Barranquero
2007-05-16 15:04         ` Károly Lőrentey
2007-05-16 15:34           ` David Kastrup
2007-05-16 16:11             ` Károly Lőrentey
2007-05-16 21:17             ` Jason Rumney
2007-05-16 16:20         ` Dan Nicolaescu
2007-05-16 17:39       ` David Kastrup
2007-05-16 20:48         ` Károly Lőrentey
2007-05-17 14:02       ` Stefan Monnier
2007-05-17 16:04         ` Károly Lo"rentey
2007-05-17 23:24           ` Stefan Monnier
2007-05-18 18:02             ` Károly Lo"rentey
2007-05-19 14:07               ` Stefan Monnier
2007-05-13 20:07 ` Jason Rumney
2007-05-14 10:21   ` Karoly Lorentey
2007-05-14 11:55     ` Jason Rumney
2007-05-15 13:03       ` Karoly Lorentey
2007-05-15 22:05     ` Ken Raeburn
2007-05-14  6:00 ` Manoj Srivastava

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='f2f0n2$dbd$1@sea.gmane.org' \
    --to=karoly@lorentey.hu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.