On 8/31/23, Wang Yizhen <wang1zhe...@gmail.com> wrote: > > I recently noticed a bug for the emacs package in sid. I have not > reported a bug before, so I wrote this email to seek for help. > > After upgraded to emacs 29.1+1-5, I found that the emacsclient command > is not working. More specifically, the following command hangs emacs in > daemon forever and no emacs frame pops up: > > ``` > > emacsclient -c -a "" -n > > ``` > > However, `emacsclient -c -a ""` summons the emacs frame properly > although it occupies the terminal.
Hi, Yizhen. I don't have experience with emacs, am just chiming in to rule out a long shot causative. Do you type that command by hand or maybe arrow up and down through existing terminal history to find that same line to reuse it all the time? Or do you copy that line off of something that might not be using plain text? The reason I ask is that on rare occasions, copy-and-pasting from something like an Internet webpage or an advanced features text editor can unintentionally introduce funky (fancy "curly") quotation marks and parentheses [0]. Those curly things can break scripts because a terminal can and will interpret curlies as a separate character from the "straight" ones. How a terminal can interpret those differently, I don't know. I just know firsthand that it can and does. I once spent MANY HOURS fighting a compiling failure or similar over this very thing. I finally stumbled upon the difference in those marks' appearances when two lines were visually different lengths in my terminal window. The difference in my case was that I had copied a command off the Internet and then manually retyped it later while trying to personalize the affected command to fit my setup. Note: The additional reason I stepped out here to ask is because those quotation marks are in front of that "-n" [flag]. It comes to mind to think that curly quotes could possibly mangle a flag following them, but a terminal command could simply ignore curlies when nothing comes after them. Hope that rationale makes at least a little sense. It does "BKAC" (between keyboard and chair). Afterthought: The reason something like curly quotes might suddenly become an issue after years of no problems is that our operating systems' code is getting "tighter" every year, i.e. less forgiving of things that really shouldn't have ever worked in the first place. That's a good thing that reflects on how Developers are perennially honing their combined skills while presenting the most dependable software packages possible... at any given nanosecond in Time. Cindy :) [0] https://chrisbracco.com/curly-quotes/ -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
