It is close to two months that I have been the only person running
test-patches, even though several volunteers claimed they would do so.
It has been the main reason I shelled out €20 for a week of internet
access during my spring vacation.
My limited computing resources mean that I have to take
Hello,
On 22 April 2012 04:12, Mark Mathias wrote:
> So... as far as the Bug Squad is concerned, are we still waiting for
> something or does this need to get added to the tracker?
> Thanks,
> Mark
>
As far as the bug squad are concerned - being one myself - we'd like a
confirmation that this is
Hello,
On 22 April 2012 00:02, Francisco Vila wrote:
> 2012/4/20 Graham Percival :
>> We do not have a long history of flawless git actions from
>> translations, so my preference would be not to touch anything.
>
> Good idea! The definitive recipe for eternal flawless development is
> not to touc
\version "2.15.36"
#(define-public lst `())
#(define (set-new-alist! ls-1 ls-2 proc)
(for-each (lambda (x) (set! ls-1 (acons x proc ls-1))) ls-2)
ls-1)
#(set-new-alist! lst '(1 2 3) "X")
#(display lst)
returns: ()
What am I missing?
%%
Well, if you change
#(set-new-alist! lst '(1 2 3)
2012/4/20 Graham Percival :
> We do not have a long history of flawless git actions from
> translations, so my preference would be not to touch anything.
Good idea! The definitive recipe for eternal flawless development is
not to touch anything, ever. Better safe than sorry.
--
Francisco Vila. Ba
Thomas Morley writes:
> Hi,
>
> the following code gives me the expected output in guile:
>
> (define-public lst `())
> (define (set-new-alist! ls-1 ls-2 proc)
> (for-each (lambda (x) (set! ls-1 (acons x proc ls-1))) ls-2)
> ls-1)
> (set-new-alist! lst '(1 2 3) "X")
>
> ==> ((3 . "X") (2 . "X
Hi,
the following code gives me the expected output in guile:
(define-public lst `())
(define (set-new-alist! ls-1 ls-2 proc)
(for-each (lambda (x) (set! ls-1 (acons x proc ls-1))) ls-2)
ls-1)
(set-new-alist! lst '(1 2 3) "X")
==> ((3 . "X") (2 . "X") (1 . "X"))
trying similiar in lily:
\v
On 2012/04/21 16:10:09, dak wrote:
The "cleanup" would seem to break layout totally.
http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/71476>
That's disappointing. The property 'previous_offset' sometimes has
values comparable to the page height. On the early returns I'll return
On 2012/04/15 20:06:55, Keith wrote:
On 2012/04/15 16:45:54, Keith wrote:
>
> An improvement would be to round-to-larger
Done, along with other cleanup following the similar function
rest_collision_callback()
The "cleanup" would seem to break layout totally.
http://permalink.gmane.org/gmane
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'lilypond' has been made available
to the language teams for translation. It is archived as:
http://translationproject.org/POT-files
Bernard Hurley writes:
> On Sat, Apr 21, 2012 at 01:49:38PM +0200, David Kastrup wrote:
>> Bernard Hurley writes:
>>
>> > That sounds interesting. Personally I would rather see Emacs
>> > re-implemented using Common Lisp instead of Emacs Lisp.
>>
>> http://common-lisp.net/project/climacs/> is
On Sat, Apr 21, 2012 at 01:49:38PM +0200, David Kastrup wrote:
> Bernard Hurley writes:
>
> > On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote:
> >>
> >> >> [1] why oh why does the main GNU editor not use the "official
> >> >> extension language for the GNU operating system"??
> >>
Le 21/04/2012 12:33, James disait :
Hello,
On 21 April 2012 10:13, Jean-Charles Malahieude wrote:
...
This makes me believe it would be a good opportunity to have the English
version follow the same rule as translations.
Err.. not sure what you mean by that technically but it's complicated
Bernard Hurley writes:
> On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote:
>>
>> >> [1] why oh why does the main GNU editor not use the "official
>> >> extension language for the GNU operating system"??
>> >
>> > Same reason why its keyboard shortcuts are only so-so compatible wit
On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote:
>
> >> [1] why oh why does the main GNU editor not use the "official
> >> extension language for the GNU operating system"??
> >
> > Same reason why its keyboard shortcuts are only so-so compatible with
> > CUA and/or GNOME: its deve
On Sat, Apr 21, 2012 at 11:33:49AM +0100, James wrote:
> Err.. not sure what you mean by that technically but it's complicated
> enough with snippets as it is, to follow the translation method adds
> even more complexity (if the CG is anything to go by).
+1
> We want to encourage contributors not
Hello,
On 21 April 2012 10:13, Jean-Charles Malahieude wrote:
...
> This makes me believe it would be a good opportunity to have the English
> version follow the same rule as translations.
Err.. not sure what you mean by that technically but it's complicated
enough with snippets as it is, to fo
Le 21/04/2012 10:57, Federico Bruni disait :
Il 17/04/2012 23:40, Francisco Vila ha scritto:
2012/4/17 Federico Bruni:
> Another solution could be keeping the current structure and
changing only
> check-translation.py so that, when looking at the files in
> Documentation/snippets, it should che
>> [1] why oh why does the main GNU editor not use the "official
>> extension language for the GNU operating system"??
>
> Same reason why its keyboard shortcuts are only so-so compatible with
> CUA and/or GNOME: its development was started more than 30 years ago,
> when nobody had ever heard of
Jean-Charles Malahieude writes:
> Le 20/04/2012 23:42, Graham Percival disait :
>> On Fri, Apr 20, 2012 at 07:38:06PM +0200, Jean-Charles Malahieude wrote:
>>> Le 19/04/2012 21:30, Graham Percival disait :
- nobody touches the release/unstable branch, other than
translators, who may
Il 17/04/2012 23:40, Francisco Vila ha scritto:
2012/4/17 Federico Bruni:
> Another solution could be keeping the current structure and changing only
> check-translation.py so that, when looking at the files in
> Documentation/snippets, it should check only the changes inside texidoc = ""
>
Le 20/04/2012 23:42, Graham Percival disait :
On Fri, Apr 20, 2012 at 07:38:06PM +0200, Jean-Charles Malahieude wrote:
Le 19/04/2012 21:30, Graham Percival disait :
- nobody touches the release/unstable branch, other than
translators, who may merge with that if they want to and don't
brea
22 matches
Mail list logo