You're right. I'm having a bad day, and it seems I'm not thinking straight. Now the question is, you were getting a "connect" error. How is that related to entering the if()? When I run emacsclient,
Hi, I figured it out... I guess. The port is same as pid of the process. I guess I had 2 sessions of emacs running and one in which server was not. The client finds the one without the server running
Recipe for reproducing the problem: 1. Start emacs with server 2. Use emacsclient to open a file (with -n option not to wait) 3. Start another emacs with server 4. Use emacsclient as in #2 (it will o
Hi, The previous email is about this problem of Emacs.app not working when dumped under GNUstep. Since I cannot work on this myself at the moment (and failed when I *did* put time into it before), le
Or just get rid of the defconst. Let's look at the code in question: (defconst dir-locals-file ".dir-locals.el" "File that contains directory-local variables. It has to be constant to enforce uniform
I can't believe we have this kind of discussion :( All packages with similar functionality have defcustom for the file name. dir-locals.el: (defcustom dir-locals-file-name ".emacs-locals" "File name
function. This has been discussed to death, and someone said it very well upthread: "it's broken by design". How was it not a constant before the change? What does that accomplish that the previous c
function. Yeah, it could have been avoided by not adding the defconst, which is quite obvious by now that was only added to circumvent the fact that the settings file name should not be changeable by
Drew Adams wrote: * The non-"nontrivial" eol convention, represented by `:', is presumably what is meant by "usually", that is, a newline char. But a newline eol is also sometimes represented by `(Un
I meant "trivial", sorry. The doc claims that line endings other than newline are nontrivial. (I think you too meant "trivial" here, for UNIX.) What's trivial for the implementation shouldn't be beh
The attached patch renames "system-process-attributes" to "process-attributes", and adds the ability to use emacs process objects as well as pids: (1) Change the signature of the system-specific syst
How many copies of this function did you add to process.c? It looks like you added only one, while I think you need 2: one each for the These are already documented in the ELisp reference manual, so
It would be cleaner to invoke some function in hi-lock.el rather than going straight into font-lock. Moreover, hi-lock-mode already has a persistence mechanism; why does desktop need to additionally
Yes, absolutely. This was more of a reminder of what need to be done. Doesn't they serve very different situations? I could for example save a desktop file for a special problem I am working on. When
I don't think they'll "expect" that, I hope they'll learn from what we tell them, part of which is the traditional emacs key-bindings. That learning is what will be easier if emacs traditional key-bi
I suppose an experienced user, like me, who uses both often[*], might be so accustomed to the differences that they would internalize them. Then they'd probably simply be _annoyed_ by the arbitrary d
Is not what you feel here more of a choice? ;-) Confusion is not generally annoying. It can also lead to curiosness. Otherwise people would not be playing games for example. (Did someone notice the n
2009/6/10 Miles Bader <address@hidden>: Thank you for the straight-forward instructions! However, this was unsuccessful as well. It's not the exact same problem, but it's still off, not displaying th
Why? The 2a format speeds up some operations and will be the default format for bzr 2.0 (to be released some weeks from now). A big convenience. If you work with feature branches, having a local mirr