From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>,
Rob Pike <robpike@gmail.com>
Subject: Re: [9fans] Acme button 2 argument expansion: feature or bug?
Date: Sat, 9 Apr 2005 09:24:45 -0700 [thread overview]
Message-ID: <2b427a06c9c9cf00177be5dd56eaf60a@telus.net> (raw)
In-Reply-To: <7359f0490504090900720a8e1d@mail.gmail.com>
But even selecting the whole string fails: the colon and line number
suffix is clobbered.
A simple non-solution is to change the dofile argument to the
getbytearg call to false, which of course kills the full path expansion
of the argument :-(, but at least doesn't kill the suffix.
I'd be happy to see the suffix not killed when the selected text was
non-null.
Paul
On 9-Apr-05, at 9:00 AM, Rob Pike wrote:
> The thinking in the underlying code, which was co-opted for this
> purpose, is that a 'word' ends at punctuation. It's pretty deeply
> rooted and would be annoying to change in general, which will
> mean hacking it for your particular purpose.
>
> Instead, I recommend just avoiding expansion in this case and
> selecting the whole string you wish to send.
>
> -rob
>
prev parent reply other threads:[~2005-04-09 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 14:28 Paul Lalonde
2005-04-09 16:00 ` Rob Pike
2005-04-09 16:24 ` Paul Lalonde [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b427a06c9c9cf00177be5dd56eaf60a@telus.net \
--to=plalonde@telus.net \
--cc=9fans@cse.psu.edu \
--cc=robpike@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.
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 NNTP newsgroup(s).