[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] non-space, paste, (???) character for inline results
From: |
Greg Minshall |
Subject: |
Re: [O] non-space, paste, (???) character for inline results |
Date: |
Wed, 31 Jan 2018 06:49:09 +0530 |
Nico,
ah, thanks!
not wanting to look gift horses, etc., but i've a question. if i
understand the change correctly
----
- (looking-at "\\<call_\\([^ \t\n[(]+\\)[([]"))
+ (looking-at "call_\\([^ \t\n[(]+\\)[([]"))
----
now something like "oncall_foo()" will be taken as "on" followed by the
inline results of call_foo(). is that right? (testing, seems to be.)
i worry that might be a bit too lenient. sometimes one might want
"oncall_foo()" to stay as "oncall_foo()". (that's why i was thinking of
some, hmm, "non-spacing break", like the string "{{{}}}", or, well,
almost anything, "\.", "\#", "#" -- maybe the cleanest? -- ...)
cheers, Greg
- [O] non-space, paste, (???) character for inline results, Greg Minshall, 2018/01/30
- Re: [O] non-space, paste, (???) character for inline results, Nicolas Goaziou, 2018/01/30
- Re: [O] non-space, paste, (???) character for inline results, Greg Minshall, 2018/01/30
- Re: [O] non-space, paste, (???) character for inline results, Nicolas Goaziou, 2018/01/30
- Re: [O] non-space, paste, (???) character for inline results,
Greg Minshall <=
- Re: [O] non-space, paste, (???) character for inline results, Nicolas Goaziou, 2018/01/31
- Re: [O] non-space, paste, (???) character for inline results, Greg Minshall, 2018/01/31
- Re: [O] non-space, paste, (???) character for inline results, Nicolas Goaziou, 2018/01/31
- Re: [O] non-space, paste, (???) character for inline results, Greg Minshall, 2018/01/31
- Re: [O] non-space, paste, (???) character for inline results, Kaushal Modi, 2018/01/31
- Re: [O] non-space, paste, (???) character for inline results, Kaushal Modi, 2018/01/31
- Re: [O] non-space, paste, (???) character for inline results, Nicolas Goaziou, 2018/01/31