From: Constantin Kulikov <zxnotdead@gmail.com>
To: Jorge Alberto Garcia <jorge.garcia.gonzalez@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Why not processing emacsclient's command line arguments with user defined functions?
Date: Mon, 18 Jan 2016 10:10:25 +0300 [thread overview]
Message-ID: <CAFkz2yo1+oAgvhBFJ-RSpgX_6QG_ZMSUHeg_2Eyc5BbwqDJFqQ@mail.gmail.com> (raw)
In-Reply-To: <CAPfrtUc9BQZMvwdgGbae12_gjp48yKVL1w4S=jjf3G7O2x=xCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
> Can you elaborate
What to eleborate here? You want a new feature for emacsclient so you go
and patch C source. Tomorrow you'l want a new commandline option.
So why no one here think about general solutions?
Emacslisp solution is always better than C. (Hooks, hooks must be
everywhere in emacs)
How it could be implemented:
(I'd say that we can use the same command-line-functions and
command-switch-alist but it could break backward compatibility, so it'll
better to use a new variables I think -- emacs-client-argumet-string or
something.)
1. emacsclient searches for 'connection related' arguments because they are
needed to know how to connect to the daemon.
2. emacsclient sends the full arguments string to the server.
3. server calls user(and predefined) hooks which must examine and do
manipulations on that string.
[-- Attachment #2: Type: text/html, Size: 1013 bytes --]
next prev parent reply other threads:[~2016-01-18 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 16:57 Why not processing emacsclient's command line arguments with user defined functions? Constantin Kulikov
2016-01-17 15:55 ` Jorge Alberto Garcia
2016-01-18 7:10 ` Constantin Kulikov [this message]
2016-01-18 16:57 ` Jorge Alberto Garcia
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFkz2yo1+oAgvhBFJ-RSpgX_6QG_ZMSUHeg_2Eyc5BbwqDJFqQ@mail.gmail.com \
--to=zxnotdead@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jorge.garcia.gonzalez@gmail.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).