On Mon, Mar 22, 2004 at 10:36:32PM -0800, David Wheeler wrote:
: I'll wait and see what I hear back from the Emacs developers.
Well, it's too bad the emacs developers are lagging behind the vim
developers in this area, but it might (or might not) have something to
do with the fact that certain obn
On Mar 22, 2004, at 10:28 PM, Piers Cawley wrote:
(require 'cl)
somewhere before that code chunk. I thought everyone already did that.
Thanks. I put only the code you sent me in my .emacs, and a handy
Unicode file I have still doesn't display properly. *sigh*
I'll wait and see what I hear back
David Wheeler <[EMAIL PROTECTED]> writes:
> On Mar 22, 2004, at 5:02 PM, Piers Cawley wrote:
>
>> Try this:
>>
>> (cond
>> ((eq window-system 'mac)
>> (when (string= default-directory "/")
>> (setq default-directory "~/"))
>> (setq mac-command-key-is-meta t
>> mac-reverse-ctrl-meta n
Austin Hastings writes:
> > ->Â @cp makes about as much sense as subÂ(@cp). C returns a
> > list of array references, right? So it binds each one to @cp (the right
> > of -> is a subroutine parameter list, remember?).
>
> Are you saying that subÂ(@cp) is not, in fact, an alias for C ?
>
> Anyw
> -Original Message-
> From: Luke Palmer [mailto:[EMAIL PROTECTED]
>
> Austin Hastings writes:
> > Before this gets simonized, let me add that this seems genuinely
> > useful: It provides a way of constructing a loop in a dimension that
> > is not really accessible, except via recursion.
Austin Hastings writes:
> Before this gets simonized, let me add that this seems genuinely
> useful: It provides a way of constructing a loop in a dimension that
> is not really accessible, except via recursion.
>
> Luke: Would that have to be
>
> for outer([EMAIL PROTECTED]) ->Â @cp {...}
>
On Tue, Mar 23, 2004 at 07:35:39AM +1100, Damian Conway wrote:
: However I do think that, now we have C to carry the load of "exists
: uniquely", Larry will probably decide that C is strictly binary, and
: hence generalizes to the "parity" form in the n-ary case.
Hmm, I probably will. :-)
But
On Mar 22, 2004, at 5:02 PM, Piers Cawley wrote:
Try this:
(cond
((eq window-system 'mac)
(when (string= default-directory "/")
(setq default-directory "~/"))
(setq mac-command-key-is-meta t
mac-reverse-ctrl-meta nil
process-connection-type nil
mac-keyboard-text-encoding kTextEncoding
> -Original Message-
> From: [EMAIL PROTECTED]
>
> [EMAIL PROTECTED] (Austin Hastings) writes:
> > Before this gets simonized, let me add that this seems
> genuinely useful: It provides a way of constructing a loop in a
> dimension that is not really accessible, except via recursion.
>
> Oh
David Wheeler <[EMAIL PROTECTED]> writes:
> On Mar 20, 2004, at 1:32 PM, Calle Dybedahl wrote:
>
>> You don't need Unicode display « and », just plain old ISO 8859-1.
>
> True, but I'd like to get Unicode working for other projects, as well.
>
>> They're characters number 171 and 187 there. And AF
[EMAIL PROTECTED] (Austin Hastings) writes:
> Before this gets simonized, let me add that this seems genuinely useful: It provides
> a way of constructing a loop in a dimension that is not really accessible, except
> via recursion.
Oh, it *is* useful, and it's extremely nice to know that someth
> -Original Message-
> From: Luke Palmer [mailto:[EMAIL PROTECTED]
>
...
> Using a permutations module I could make that shorter, but I figure that
> since we're already providing C to make looping easier, why not
> provide C (perhaps spelled Â)? The outer function would provide
>
Luke Palmer writes:
> Which is of course wrong.
>
> sub _outer_coro(@prev, @data) is coroutine
> {
> if (@data) {
> _outer_coro([ @prev, @data[0] ], @data[1...])
> }
> else {
> yield [EMAIL PROTECTED];
> }
> }
>
> sub outer([
Luke Palmer writes:
> I believe it could be programmed lazily. Like this:
>
> sub _outer_coro(*$first is context(Scalar),
> [EMAIL PROTECTED] is context(Scalar))
> is coroutine
> {
> if @rest {
> _outer_coro [EMAIL PROTECTED];
> }
I found myself writing a perl script today in which I did (I'll
perl6-ize it for sake of discussion):
for 98,99 -> $i {
for 0..255 -> $j {
# testing IP addresses with $i.$j
}
}
I was thinking about what would happen if I allowed the user to input
those ranges,
John Macdonald wrote:
if ($a xor $b xor $c) {...}
should succeed only when exactly one of ($a, $b, $c) is true.
That's not the definition of xor that I learned in school.
It's taking a simplified form of the definition that works
for two arguments and then expanding it to multiple
arguments -
Mark J. Reed wrote:
One obvious reason for reaching out to unicode characters is the
restricted number of non-alphanumeric characters in ASCII. But why do
infix operators have to be non-alphanumeric?
They don't - but they do have to "look like operators". Thanks to the
multiplication symbol, lowe
On Mar 20, 2004, at 1:32 PM, Calle Dybedahl wrote:
You don't need Unicode display « and », just plain old ISO 8859-1.
True, but I'd like to get Unicode working for other projects, as well.
They're characters number 171 and 187 there. And AFAIK every Emacs
version released in the past ten years ha
Juerd: your message arrived in my inbox as an attachment due to a mail server
along the way not recognizing the "charset" value. It should be "utf-8"
with the hyphen, not "utf8". Also for that reason all the non-ASCII
characters (like the Yen symbol) came through as '?' here.
> Kara Perlistoj,
On 2004-03-20 at 22:32:18, Calle Dybedahl wrote:
> You don't need Unicode display « and », just plain old ISO 8859-1.
> They're characters number 171 and 187 there. And AFAIK every Emacs
> version released in the past ten years handles ISO-8859-1 out of the
> box. It's more likely that you're usin
Austin Hastings said:
> Let's look at boolean xor:
>
> if ($a xor $b xor $c) {...}
>
> should succeed only when exactly one of ($a, $b, $c) is true.
I think it is generally accepted that xor is true iff an odd nnumber of
its argumnets are true.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.
> "David" == David Wheeler <[EMAIL PROTECTED]> writes:
> Nice to know, even though my Emacs only displays empty squares for
> these characters. I have yet to figure out how to get it to properly
> display Unicode
You don't need Unicode display « and », just plain old ISO 8859-1.
They're char
On Sat, Mar 20, 2004 at 03:09:15PM -0500, Austin Hastings wrote:
> Let's look at boolean xor:
>
> if ($a xor $b xor $c) {...}
>
> should succeed only when exactly one of ($a, $b, $c) is true. This corresponds
> roughly to constructing and then collapsing a one() junction:
That's not the defin
23 matches
Mail list logo
