Fwd: Using Vim's logo for a tabletop game
The attachment is a request from some game developers addressed to the Vim
community, requesting the use of Vim's logo in a game. (As a token of some
sort, based on the request.)
If they haven't already requested it from the Perl or Raku communities, on
the face of it, offering them our logos would be a good idea. (Subject to
due diligence and careful consideration of the game and its developers.)
--- Begin Message ---
Dear Vim community,
We hope this message finds you well. We are Clara Jiménez Recio and Celia
Velasco Martínez and we are excitedly embarking on a personal project to
create a tabletop game with a focus on the dev community.
The mechanics of our game, tentatively titled "try {} catch (it)", involve
working with more than 50 logos of different programming tools. Multiple
logos will appear on each card, and the gameplay is centered around
identifying the matching logo in each pair of cards.
We are wondering whether it would be okay to include Vim's logo within the
game. Of course, any required disclaimer would be included.
Many thanks,
Clara and Celia
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/f5fc5b1e-c8ff-4f10-851e-c1209cf04e9en%40googlegroups.com.
--- End Message ---
Re: [perl #44657]
> Apparently the plan is to go in the opposite direction, i.e., getting that > stuff out of the Parrot distribution and into Bundle::Parrot on CPAN. How would the naming work there? I was trying to reduce the amount of keying required to invoke functions, and to keep their invocation the same as if they had been installed "normally". That would eliminate the need for any additional documentation, (other than perhaps a statement that "if you install this, you will have Foo::Bing, Bar::*, and Bam::Bam available", or something similar).
More bugs or PEBKAC
1. Should there be a way to make "die" behave like the Perl 5 version,
reporting the place of death unless the message is terminated by \n ?
The \n no longer suppresses the location indormation. I can't find a
definition either way in the Synopses.
2. The following code (c_to_f) is broken: (I subsequently found the
correct way to loop over the 0..20 values)
#! /home/guru/bin/perl6
my $c;
for $c = 0..20 {
say $c;
my $f = ($c * 9 / 5) +32;
say $f;
}
It produces the following result:
$ ./c_to_f
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
69.8
"Say" is clearly treating $c as an array in some way, but the arithmetic
is using a value of 21 (the number of array elements) in $c. Is there a
reasonable explanation for what's happening?
3. The following is an edited transcript of a session playing with ...
(the comment lines inserted afterwards). Are they the intended results?
$ perl6 -e 'say "Yo"; {...} ; say "Bye" '
Yo
# Unannounced demise
$ perl6 -e 'say "Yo"; {???} ; say "Bye" '
Yo
Stub code executed in at line 1
Null PMC access in setprop()
in main program body at line 1
# Is this message correct?
$ perl6 -e 'say "Yo"; {!!!} ; say "Bye" '
Yo
Stub code executed
in main program body at line 1
# Reasonable, according to the synopsis
$ perl6 -e 'say "Yo"; { } ; say "Bye" '
Yo
Bye
# Again, reasonable beaviour
$ perl6 -e 'say "Yo"; if !{...} { say "Bye"} '
Yo
$ perl6 -e 'say "Yo"; if {...} { say "Bye"} '
Yo
Bye
# The opposite to what I'd expect, if ... returns failure
$ perl6 -e 'say "Yo"; say {...} '
Yo
_block1063
# What is that? The reference to an anonymous subroutine?
$ perl6 -e 'say "Yo"; if {...} { }; say "Bye" '
Yo
Bye
# Reasonable
I would have submitted this through my usual account at GMail, but GMail
says it "has detected unusual activity on my account", and wants to send
me a confirmation code on a cellphone.
A) I don't own a cellphone, and
B) wouldn't give Google the number if I did.
