help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Use regex in ~/.emacs.d/init.el to match no_proxy.


From: Hongyi Zhao
Subject: Re: Use regex in ~/.emacs.d/init.el to match no_proxy.
Date: Sun, 11 Apr 2021 08:04:39 +0800

On Sat, Apr 10, 2021 at 10:08 PM Joost Kremers <joostkremers@fastmail.fm> wrote:
>
>
> On Sat, Apr 10 2021, Hongyi Zhao wrote:
> > On Thu, Apr 8, 2021 at 2:29 PM Joost Kremers <joostkremers@fastmail.fm> 
> > wrote:
> > Really, it does the trick:
> >
> > ~ $ (regexp-opt '("*.cn" "localhost" "10.0.0.0/8" "127.0.0.0/8"
> > "172.16.0.0/12" "192.168.0.0/16"))
> > \(?:\*\.cn\|1\(?:0\.0\.0\.0/8\|27\.0\.0\.0/8\|72\.16\.0\.0/12\|92\.168\.0\.0/16\)\|localhost\)
> >
> >> For Lisp interaction, I'd recommend `M-x ielm`, though.
> >
> > This also works like a charm:
> >
> > ELISP> (regexp-opt '("*.cn" "localhost" "10.0.0.0/8" "127.0.0.0/8"
> > "172.16.0.0/12" "192.168.0.0/16"))
> > "\\(?:\\*\\.cn\\|1\\(?:0\\.0\\.0\\.0/8\\|27\\.0\\.0\\.0/8\\|72\\.16\\.0\\.0/12\\|92\\.168\\.0\\.0/16\\)\\|localhost\\)"
> >
> > But why the 2nd method gives the double '\\' escaped sequence for some
> > metacharacters while the the 1st method doesn't?
>
> They are different representations of the same thing. In IELM, the return 
> value
> is a string, as indicated by the double quotes surrounding the regexp. This is
> what you would use in your init file (or in a Lisp program). Eshell prints the
> string, i.e., shows you the string in a form that's meant for humans to look 
> at.

This is just what I wonder. Why can't we let Emacs use the
human-readable regexp string representation in its init file?

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Polytechnic University of Science and Technology engineering
NO. 552 North Gangtie Road, Xingtai, China



reply via email to

[Prev in Thread] Current Thread [Next in Thread]