What do you mean by resizing flicker? I've never seen it with the
multi-line tags. And we do resize the tag by hand - the scroll wheel opens
and shuts it, in addition to adding/removing the trailing newline.
On Mon Oct 27 2014 at 8:44:57 PM erik quanstrom
wrote:
> On Mon Oct 27 19:39:19 EDT 20
On Mon Oct 27 19:39:19 EDT 2014, paul.a.lalo...@gmail.com wrote:
> We (Russ and I) never ported it back to Plan9 because there's a subtle
> layout bug when columns have different height fonts for the tag and the
> body. I works well enough for us, but isn't at the quality it should be.
the layou
We (Russ and I) never ported it back to Plan9 because there's a subtle
layout bug when columns have different height fonts for the tag and the
body. I works well enough for us, but isn't at the quality it should be.
Paul
On Mon Oct 27 2014 at 3:57:01 PM Rob Pike wrote:
> That's a shame.
>
> -r
Thanks! I just tested it. It works!
On Sun, Oct 26, 2014 at 5:52 PM, David du Colombier <0in...@gmail.com>
wrote:
> Just to be clearer. The patch (unified diff) attached in my
> previous email can be applied with ape/patch.
>
> A patch(1) (/n/sources/patch) can't be applied automatically
> withou
That's a shame.
-rob
On Mon, Oct 27, 2014 at 9:41 AM, wrote:
>> Yes you can. That's how I verified this works. Open up the tag to
>> multiple lines (just type newline in the tag).
>
> I think this only works in p9p.
>
> sl
>
I have a simple C program:
#include
void main()
{
print("abc\n");
exits(nil);
}
I built it under Linux using ken-cc (the Linux port of the Plan 9
compilers). However, this happens when I try to link it:
8l -L/home/ryan/stuff/ken-cc/Linux/386/lib -l9 -o test test.8
main: undefined: prin
> Yes you can. That's how I verified this works. Open up the tag to
> multiple lines (just type newline in the tag).
I think this only works in p9p.
sl
On Mon Oct 27 12:34:58 EDT 2014, lu...@proxima.alt.za wrote:
> > one does not have to put eve in adm or especially sys. in fact, i think
> > this
> > makes one's system significantly less secure.
>
> It's complicated, in that access controls are enforced by distinct
> entities with potentially v
Plan 9's Acme doesn't support multiline (at least not version I have).
The way you can do it is to put the multiline instructions for Edit in a
different buffer; then select the multiline instructions and middle-left
click on Edit of the file you want to edit.
On Mon, Oct 27, 2014 at 10:09 AM, R
On Mon, Oct 27, 2014 at 10:09:46AM -0700, Rob Pike wrote:
> Yes you can. That's how I verified this works. Open up the tag to
> multiple lines (just type newline in the tag).
>
> -rob
Yes, it worked thank you for your help.
--
Eduardo Alvarez
"Stercus, Stercus, Stercus, moriturus sum"
-- Ri
> Yes you can. That's how I verified this works. Open up the tag to
> multiple lines (just type newline in the tag).
I use the plan9 legacy version, that seems to ignore typed newlines. With the
p9p it works and possible with the 9front version too.
Actually I can echo 'Edit {…
}'>/mnt/acme/{win
At least p9p acme has multiline tags. Personally, I prefer 2-1 chord
complicated or frequent stuff onto Edit command
--
Kostarev Ilya
On 27 Oct 2014 at 18:48:10, Ingo Krabbe (ikrabbe@gmail.com) wrote:
but you can't do this on a acme headline. So how would you apply such multiline
> Yes you can. That's how I verified this works. Open up the tag to
> multiple lines (just type newline in the tag).
And in any event, the multiline Edit command can be executed from
within the editable text, where vertical space is not usually at a
premium. Takes some tidying up afterwards, but
Yes you can. That's how I verified this works. Open up the tag to
multiple lines (just type newline in the tag).
-rob
> one does not have to put eve in adm or especially sys. in fact, i think this
> makes one's system significantly less secure.
It's complicated, in that access controls are enforced by distinct
entities with potentially very distinct criteria. Trying to conceive
all possible combination of clien
> Under plan9 the user who boots a machine has rights to its filesystem,
> so unless you are accessing a remote plan9 file server which is running
> an auth server I doubt your problems are to do with administration rights.
in practice, it often works out this way. especially because the file ser
> you make a good point.
David did explain. It's fixed in the patch.
Lucio.
-
This email has been scanned by the MxScan Email Security System.
---
On Mon Oct 27 00:22:36 EDT 2014, lu...@proxima.alt.za wrote:
> > @@ -1594,6 +1595,7 @@
> > static Ints7 oid_md4WithRSAEncryption = {7, 1, 2, 840, 113549, 1, 1, 3 };
> > static Ints7 oid_md5WithRSAEncryption = {7, 1, 2, 840, 113549, 1, 1, 4 };
> > static Ints7 oid_sha1WithRSAEncryption ={7, 1, 2,
but you can't do this on a acme headline. So how would you apply such multiline
commands to a range you marked in the buffer?
> Edit {
> s/^/\[/
> s/\:\ /\]/
> }
>
>
> On Mon, Oct 27, 2014 at 8:28 AM, Eduardo Alvarez
> wrote:
>
>> Hello, everyone,
>>
>> I'm in the process of learning acme via
On Mon Oct 27 05:20:04 EDT 2014, 9f...@hamnavoe.com wrote:
> > A patch(1) (/n/sources/patch) can't be applied automatically
> > without modifying patch/apply.
>
> Actually it can, thanks to the magic of bind(1):
>
> cpu% 9fs sources
> cpu% PATCH=libsec-x509-sha256rsa
> cpu% mkdi
Edit {
s/^/\[/
s/\:\ /\]/
}
On Mon, Oct 27, 2014 at 8:28 AM, Eduardo Alvarez
wrote:
> Hello, everyone,
>
> I'm in the process of learning acme via Russ Cox's p9p port. Recently, I
> found
> myself editing some text to use with markdown, and needed to make more
> than one
> modification to a lis
Hello, everyone,
I'm in the process of learning acme via Russ Cox's p9p port. Recently, I found
myself editing some text to use with markdown, and needed to make more than one
modification to a list. I wanted to know if it's possible to give the Edit
command more than one argument. For example, I
> A patch(1) (/n/sources/patch) can't be applied automatically
> without modifying patch/apply.
Actually it can, thanks to the magic of bind(1):
cpu% 9fs sources
cpu% PATCH=libsec-x509-sha256rsa
cpu% mkdir -p $home/patch/$PATCH
cpu% bind -bc $home/patch/$PATCH /n/s
> It was a typo. I fixed it before submitting the patch to /n/sources.
I thought it might be; better safe than sorry, I suppose.
Lucio.
-
This email has been scanned by the MxScan Email Security System.
24 matches
Mail list logo
