mailing-list for TeXmacs Users

["Z.WU" <address@hidden>]

True, that is the only way to close it properly.

------------------ ???????? ------------------

??????: Ben shimol Yehuda <address@hidden>

????????: 2016??4??30?? 16:07

??????: Z.WU <address@hidden>

????: texmacs-users <address@hidden>

????: Re: [TeXmacs] No response after CMD-w to close window on TeXmacs1.99.4 OS X

For me it is the same experience using ver 1.99.4 on MAC OS X

I prefer to practically quit TM (using CMD+Q) and reopen rather than ??close?? (which is not successful anyway)

yehuda

---
Yehuda

On Apr 29, 2016, at 6:22 PM, Z.WU <address@hidden> wrote:

It is not the first case. Actually, when I open TeXmacs the first time, and try to close the window, I notice the yes or no choice.  But this time it is really not that case, the Activity  Monitor also shows red line on TeXmacs with not responding.

------------------ Original ------------------

From:  "David G. Wonnacott";<address@hidden>;

Send time: Friday, Apr 29, 2016 7:56 PM

To: "Z.WU"<address@hidden>; "texmacs-users"<address@hidden>;

Subject:  Re: [TeXmacs] No response after CMD-w to close window on TeXmacs 1.99.4 OS X

When I show students how to use TeXmacs, sometimes I find that they overlook a prompt at the bottom of the main window, e.g. a question about saving files before quitting. This can cause the symptoms you describe: TeXmacs won't do *anything* until you answer that question.

I think there is a way to set preferences to have TeXmacs ask such questions appear in a separate pop-up window.

Or, it could be a bug I've not seen.

-- Dave W (sent from my phone, so please excuse brevity, speak-o's, and swype-o's)

On April 29, 2016 4:23:24 AM EDT, "Z.WU" <address@hidden> wrote:

Hi, guys,

This is Steven. I have one question while using TeXmacs 1.99.4 OS X version. When I press CMD-w to close a file, the TeXmacs window turns to be dead (not responding). The only way is to force to quit.  I tried  to reinstall it, but still the same problem there. However, after downgrading to 1.99.1, this problem does not show up.

Any ideas?

Thx