9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Joseph Xu <josephzxu@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] wierd behaviour in acme (plan9port)
Date: Thu, 11 Mar 2010 02:37:23 -0500	[thread overview]
Message-ID: <4B989DB3.2050309@gmail.com> (raw)
In-Reply-To: <c3b67e041003102219m476ed73ch3ef792e71f1f68d2@mail.gmail.com>

On 3/11/2010 1:19 AM, lorenzo vegro wrote:
> Thank you, I will look into it.  I also noticed that if I run acme as
> root, win works as expected: is this in any way relevant?
>
> -Lorenzo
>
> 2010/3/10, Joseph Xu<josephzxu@gmail.com>:
>> On 03/10/2010 01:34 PM, lorenzo vegro wrote:
>>> hello,
>>> I am experiencing quite a strange behaviour with acme in plan9port:
>>> whenever I 2-click "win" in acme, the window actually shows up as it
>>> is supposed to, but without any prompt, as if it were an empty file.
>>> If I try to send a command within the window, it has no effect.
>>> Moreover, if I 2-click "Send" when on the first line of the empty
>>> window, acme crashes sending the message "acme: bufread: internal
>>> error: Success".  I probably should add that I just reinstalled p9p
>>> and all the dependecies, so I assume they're all the latest version.
>>> Have anyone else experienced this?  Do you have any idea on what might
>>> be causing this? Any help would be greatly appreciated.
>>> Thanks.
>>>
>>> -Lorenzo
>>>
>>
>> Hi Lorenzo:
>>
>> Others have experienced this in the past too. Here's the thread with the
>> relevant discussion:
>>
>> http://bitbucket.org/rsc/plan9port/issue/37/9term-exiting-with-no-ptys
>>
>>
>
Maybe it has to do with the permissions in /dev/pts? I really don't
know, sorry.



      reply	other threads:[~2010-03-11  7:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 18:34 lorenzo vegro
2010-03-10 19:39 ` Joseph Xu
2010-03-11  6:19   ` lorenzo vegro
2010-03-11  7:37     ` Joseph Xu [this message]

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=4B989DB3.2050309@gmail.com \
    --to=josephzxu@gmail.com \
    --cc=9fans@9fans.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).