zsh-workers
 help / color / mirror / code / Atom feed
From: Kwon Yeolhyun <yeolhyunkwon@me.com>
To: Peter Stephenson <p.stephenson@samsung.com>,
	Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh List Hackers' <zsh-workers@zsh.org>
Subject: Re: Unicode, Korean, normalization form, Mac OS X and tab completion
Date: Tue, 03 Jun 2014 00:48:13 +0900	[thread overview]
Message-ID: <F0CF637B-4D42-4109-BA2E-F5EDF1E77ED9@me.com> (raw)
In-Reply-To: <20140602162711.6ce4c884@pwslap01u.europe.root.pri>

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]


On Jun 3, 2014, at 12:27 AM, Peter Stephenson <p.stephenson@samsung.com> wrote:

> On Mon, 02 Jun 2014 08:14:26 -0700
> Bart Schaefer <schaefer@brasslantern.com> wrote:
>> On Jun 2, 11:23pm, Kwon Yeolhyun wrote:
>> } 
>> } After the patch, I changed my login shell to the zsh.
>> } 
>> } $ sudo chsh -s /usr/local/bin/zsh yeolhyunkwon
>> } 
>> } Then, the terminal is closed immediately after open.
>> 
>> Hm.  Can you try putting
>> 
>> exec 2> $HOME/zsh-errors
>> set -x
>> 
>> at the top of your ~/.zshenv file and see whether anything is written
>> to the zsh-errors file?  If so, what is at the tail of it?
> 
> I wonder if it's a missing library.  In which case any report might go
> somewhere else, e.g. the equivalent of the X windows session log.
> 
> pws

I can’t find the cause of the problem. But after reinstalling oh-my-zsh, it’s working properly.

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

  reply	other threads:[~2014-06-02 15:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31  3:56 Kwon Yeolhyun
2014-05-31 15:21 ` Chet Ramey
2014-05-31 18:47   ` Bart Schaefer
2014-05-31 19:16 ` Peter Stephenson
2014-05-31 21:29   ` Bart Schaefer
2014-06-01  2:25     ` Daniel Shahaf
2014-06-01  5:30       ` Kwon Yeolhyun
2014-06-01 16:53         ` Daniel Shahaf
2014-06-01  7:56       ` Bart Schaefer
2014-06-01 16:46         ` Daniel Shahaf
2014-06-01 17:00         ` Jun T.
2014-06-01 19:13           ` Bart Schaefer
2014-06-02 17:01             ` Jun T.
2014-06-02 17:14               ` Bart Schaefer
2014-06-01 19:53           ` Bart Schaefer
2014-06-02 11:58             ` Kwon Yeolhyun
2014-06-02 14:23               ` Kwon Yeolhyun
2014-06-02 15:14                 ` Bart Schaefer
2014-06-02 15:27                   ` Peter Stephenson
2014-06-02 15:48                     ` Kwon Yeolhyun [this message]
2014-06-02 15:27                   ` Kwon Yeolhyun
2014-06-02 15:49                     ` Bart Schaefer
2014-06-02 15:58                       ` Kwon Yeolhyun
2014-06-02 14:31               ` Bart Schaefer
2014-06-02 17:15             ` Jun T.
2014-06-02 17:27               ` Bart Schaefer
2014-06-05 14:34                 ` Jun T.
2014-06-05 15:00                   ` Bart Schaefer
2014-06-02  5:17           ` Kwon Yeolhyun
2014-06-02  7:39             ` Jun T.
2014-06-02  8:42               ` Kwon Yeolhyun

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=F0CF637B-4D42-4109-BA2E-F5EDF1E77ED9@me.com \
    --to=yeolhyunkwon@me.com \
    --cc=p.stephenson@samsung.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

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).