%C

%C

[Lars Magne Ingebrigtsen]

I've now implemented the %C spec (with text props), and it seems to
work OK.  While I'm at it -- there was some question about a TAB-like
specifier, that would say "go to column X".  Would that be useful?
The syntax would be something like

  %50T   to go to column 50
  %-50T  to go to column 50 -- possibly deleting text that's already
         been inserted to get to the column

The negative lengths would be "hard" goals while the positive would be
"soft" goals.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: %C

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I've now implemented the %C spec (with text props), and it seems to
> work OK.  While I'm at it -- there was some question about a TAB-like
> specifier, that would say "go to column X".  Would that be useful?
> The syntax would be something like
>
>   %50T   to go to column 50
>   %-50T  to go to column 50 -- possibly deleting text that's already
>          been inserted to get to the column
>
> The negative lengths would be "hard" goals while the positive would be
> "soft" goals.

And it's now in CVS.  Even documented.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: %C

[Björn Torkelsson]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I've now implemented the %C spec (with text props), and it seems to
> work OK.  While I'm at it -- there was some question about a TAB-like
> specifier, that would say "go to column X".  Would that be useful?
> The syntax would be something like

%C is not working if the spec begins with %C, i.e %C%U%R...
then I get:

Args out of range: #<buffer " *gnus work*">, 0, 1

>   %50T   to go to column 50
>   %-50T  to go to column 50 -- possibly deleting text that's already
>          been inserted to get to the column

shouldn't T be = ? Or do I missinterpret the docs?

By the way both %C and %nn= (or %nnT) is missing in the
gnus-summary-line-format description.

/torkel

Re: %C

[Lars Magne Ingebrigtsen]

torkel@acc.umu.se (Björn Torkelsson) writes:

> %C is not working if the spec begins with %C, i.e %C%U%R...
> then I get:
>
> Args out of range: #<buffer " *gnus work*">, 0, 1

Hm; yes.  One can't use zero-width text props (which is how %C is
implemented), so it sets the property on the preceding character.  And
that's not possible when the %C comes first.

Although I guess I could just special-case for that and just leave the
text prop off entirely if it comes first.  That will leave point at
the start of the line.  (Except when there's a colon on the line.)

>>   %50T   to go to column 50
>>   %-50T  to go to column 50 -- possibly deleting text that's already
>>          been inserted to get to the column
>
> shouldn't T be = ? Or do I missinterpret the docs?

I changed my mind between writing the mail and writing the code.  It's
"%=". 

> By the way both %C and %nn= (or %nnT) is missing in the
> gnus-summary-line-format description.

None of the general specs are described in any of the specific line
format doc strings.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen