- Gambit-list - mailman.iro.umontreal.ca

Fwd: Printing unicode characters in Gambit
by Vijay Mathew 26 Jui '16

26 Jui '16

---------- Forwarded message ---------- From: Vijay Mathew <vijay.the.lisper(a)gmail.com> Date: Sun, Jun 26, 2016 at 10:51 AM Subject: Re: [gambit-list] Printing unicode characters in Gambit To: Adam <adam.mlmb(a)gmail.com> Thanks Adam, will try what you suggested. But I really don't understand why a special switch is required to properly print Unicode characters. Even if the user is unaware of this, 'print' going into a loop is bad behavior. --Vijay On Jun 26, 2016 8:26 AM, "Adam" <adam.mlmb(a)gmail.com> wrote: > You need to switch on unicode output for the output medium (gsc -t8) and > maybe also specify the maximum unicode character number that the writer > will accept to write. Please report back when you figured. > > 2016-06-26 10:34 GMT+08:00 Vijay Mathew <vijay.the.lisper(a)gmail.com>: > >> How can I make gambit to print a Unicode character's symbol (or glyph)? >> For example, I want to display the Unicode infinity symbol ∞ (#\u221E). >> Calling `(display #\u221E)` or `(print #\u221E)` throws the REPL into an >> infinite loop. >> (This happens for most Unicode literals I tried, not just the infinity >> symbol :-)) >> >> $ gsc >> Gambit v4.8.4 >> >> > (print #\u221E) >> *** ERROR IN ##wr-ch -- Can't convert to C char-string >> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >> >> Thanks, >> >> --- Vijay >> >> >> _______________________________________________ >> Gambit-list mailing list >> Gambit-list(a)iro.umontreal.ca >> https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list >> >> >

2 3

Re: [gambit-list] Printing unicode characters in Gambit
by Adam 26 Jui '16

26 Jui '16

Print going into a loop is not OK, I suppose Marc fixes that. Needing a switch for switching on Unicode is OK though. When that option is off, you could do your prints by serializing to UTF8 binary yourself and then writing it byte by byte to the console. 2016-06-26 13:21 GMT+08:00 Vijay Mathew <vijay.the.lisper(a)gmail.com>: > Thanks Adam, will try what you suggested. But I really don't understand > why a special switch is required to properly print Unicode characters. Even > if the user is unaware of this, 'print' going into a loop is bad behavior. > > --Vijay > > On Jun 26, 2016 8:26 AM, "Adam" <adam.mlmb(a)gmail.com> wrote: > >> You need to switch on unicode output for the output medium (gsc -t8) and >> maybe also specify the maximum unicode character number that the writer >> will accept to write. Please report back when you figured. >> >> 2016-06-26 10:34 GMT+08:00 Vijay Mathew <vijay.the.lisper(a)gmail.com>: >> >>> How can I make gambit to print a Unicode character's symbol (or glyph)? >>> For example, I want to display the Unicode infinity symbol ∞ (#\u221E). >>> Calling `(display #\u221E)` or `(print #\u221E)` throws the REPL into an >>> infinite loop. >>> (This happens for most Unicode literals I tried, not just the infinity >>> symbol :-)) >>> >>> $ gsc >>> Gambit v4.8.4 >>> >>> > (print #\u221E) >>> *** ERROR IN ##wr-ch -- Can't convert to C char-string >>> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >>> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >>> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >>> (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string >>> >>> Thanks, >>> >>> --- Vijay >>> >>> >>> _______________________________________________ >>> Gambit-list mailing list >>> Gambit-list(a)iro.umontreal.ca >>> https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list >>> >>> >>

1 0

Printing unicode characters in Gambit
by Vijay Mathew 25 Jui '16

25 Jui '16

How can I make gambit to print a Unicode character's symbol (or glyph)? For example, I want to display the Unicode infinity symbol ∞ (#\u221E). Calling `(display #\u221E)` or `(print #\u221E)` throws the REPL into an infinite loop. (This happens for most Unicode literals I tried, not just the infinity symbol :-)) $ gsc Gambit v4.8.4 > (print #\u221E) *** ERROR IN ##wr-ch -- Can't convert to C char-string (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string (write-char #\*** ERROR IN ##wr-ch -- Can't convert to C char-string Thanks, --- Vijay

2 1

{Spam?} must have
by goetter＠mazama.net 24 Jui '16

24 Jui '16

Hey, I've seen some cool stuff on the web, this is definitely must have of the season! Look at it here <http://questushuzu.skinnydipcandles.com/aephhmep> Typos courtesy of my iPhone, goetter(a)mazama.net

1 0

Any way in the Scheme code to get filename, define name and line number at compile time for debug?
by Adam 24 Jui '16

24 Jui '16

Marc, is there any way I can get the sourcecode filename, name of global define, and line number, that a particular line was compiled at? E.g. (so here, ##file, ##in-define and ##line would be output by the macro so the compiler would actually compile those at line 3, 6 and 8.) (define-macro (loc) `(print "This was printed at " ##file " in define " ##in-define " line " ##line "\n")) (loc) (define (something) (loc)) (loc) ? Thanks.

2 1

Re: [gambit-list] Can I imply a FORCE all over? (**Prio Q for this weekend or so :D )
by Bradley Lucier 09 Jui '16

09 Jui '16

I'm taking the liberty of adding the Gambit mail list to the CC, since this may be of general interest. "make check" fails after configuring with ./configure 'CC=/usr/local/gcc-6.1.0/bin/gcc -march=native' '--enable-single-host' '--enable-multiple-versions' '--enable-shared' --enable-auto-forcing "make -i check" (to ignore errors and continue) gives ------------ TEST 1 (debugging support) LD_LIBRARY_PATH=../lib:../gsi:../gsc:/usr/local/Gambit/current/lib:/usr/local/netpbm10/lib:/usr/local/gcc-6.1.0/lib/: ../gsi/gsi -:~~bin=../bin,~~lib=../lib,~~include=../include -f debug.scm > test1.out diff test1.ok test1.out && rm -f test1.out 81a82 > #return(##cprc-if2 3) : ($code rte) 85a87 > #return(##cprc-if3 3) : ($code rte) 108a111 > #return(##cprc-cond-if 3) : ($code rte) 112a116 > #return(##cprc-cond-or 3) : ($code rte) 117,120c121,126 < #return(##cprc-cond-send-red 3) : ($code rte pred) < #procedure(##cprc-cond-send-red 4) < #return(##cprc-cond-send-red 5) : ($code rte oper) < #return(##cprc-cond-send-red 6) : ($code rte) --- > #return(##cprc-cond-send-red 3) : ($code rte) > #return(##cprc-cond-send-red 4) : ($code rte pred) > #return(##cprc-cond-send-red 5) : ($code rte pred) > #procedure(##cprc-cond-send-red 6) > #return(##cprc-cond-send-red 7) : ($code rte oper) > #return(##cprc-cond-send-red 8) : ($code rte) 125,127c131,135 < #return(##cprc-cond-send-sub 3) : ($code rte pred) < #return(##cprc-cond-send-sub 4) : ($code rte oper) < #return(##cprc-cond-send-sub 5) : ($code rte) --- > #return(##cprc-cond-send-sub 3) : ($code rte) > #return(##cprc-cond-send-sub 4) : ($code rte pred) > #return(##cprc-cond-send-sub 5) : ($code rte pred) > #return(##cprc-cond-send-sub 6) : ($code rte oper) > #return(##cprc-cond-send-sub 7) : ($code rte) 131a140 > #return(##cprc-or 3) : ($code rte) 135a145 > #return(##cprc-and 3) : ($code rte) 140c150,151 < #return(##cprc-case 3) : (rte $code) --- > #return(##cprc-case 3) : ($code rte) > #return(##cprc-case 4) : (rte $code) 250,251c261,263 < #procedure(##cprc-app0-red 3) < #return(##cprc-app0-red 4) : ($code rte) --- > #return(##cprc-app0-red 3) : ($code rte) > #procedure(##cprc-app0-red 4) > #return(##cprc-app0-red 5) : ($code rte) 257,259c269,272 < #procedure(##cprc-app1-red 4) < #return(##cprc-app1-red 5) : ($code rte oper) < #return(##cprc-app1-red 6) : ($code rte) --- > #return(##cprc-app1-red 4) : ($code rte oper) > #procedure(##cprc-app1-red 5) > #return(##cprc-app1-red 6) : ($code rte oper) > #return(##cprc-app1-red 7) : ($code rte) 266,268c279,282 < #procedure(##cprc-app2-red 5) < #return(##cprc-app2-red 6) : ($code rte oper) < #return(##cprc-app2-red 7) : ($code rte) --- > #return(##cprc-app2-red 5) : ($code rte oper arg1) > #procedure(##cprc-app2-red 6) > #return(##cprc-app2-red 7) : ($code rte oper) > #return(##cprc-app2-red 8) : ($code rte) 276,278c290,293 < #procedure(##cprc-app3-red 6) < #return(##cprc-app3-red 7) : ($code rte oper) < #return(##cprc-app3-red 8) : ($code rte) --- > #return(##cprc-app3-red 6) : ($code rte oper arg1 arg2) > #procedure(##cprc-app3-red 7) > #return(##cprc-app3-red 8) : ($code rte oper) > #return(##cprc-app3-red 9) : ($code rte) 287,289c302,305 < #procedure(##cprc-app4-red 7) < #return(##cprc-app4-red 8) : ($code rte oper) < #return(##cprc-app4-red 9) : ($code rte) --- > #return(##cprc-app4-red 7) : ($code rte oper arg1 arg2 arg3) > #procedure(##cprc-app4-red 8) > #return(##cprc-app4-red 9) : ($code rte oper) > #return(##cprc-app4-red 10) : ($code rte) 297,298c313,315 < #procedure(##cprc-app-red 6) < #return(##cprc-app-red 7) : ($code rte) --- > #return(##cprc-app-red 6) : ($code rte oper) > #procedure(##cprc-app-red 7) > #return(##cprc-app-red 8) : ($code rte) 303a321 > #return(##cprc-app0-sub 4) : ($code rte) 310c328,329 < #return(##cprc-app1-sub 5) : ($code rte) --- > #return(##cprc-app1-sub 5) : ($code rte oper) > #return(##cprc-app1-sub 6) : ($code rte) 317,318c336,338 < #return(##cprc-app2-sub 5) : ($code rte oper) < #return(##cprc-app2-sub 6) : ($code rte) --- > #return(##cprc-app2-sub 5) : ($code rte oper arg1) > #return(##cprc-app2-sub 6) : ($code rte oper) > #return(##cprc-app2-sub 7) : ($code rte) 326,327c346,348 < #return(##cprc-app3-sub 6) : ($code rte oper) < #return(##cprc-app3-sub 7) : ($code rte) --- > #return(##cprc-app3-sub 6) : ($code rte oper arg1 arg2) > #return(##cprc-app3-sub 7) : ($code rte oper) > #return(##cprc-app3-sub 8) : ($code rte) 336,337c357,359 < #return(##cprc-app4-sub 7) : ($code rte oper) < #return(##cprc-app4-sub 8) : ($code rte) --- > #return(##cprc-app4-sub 7) : ($code rte oper arg1 arg2 arg3) > #return(##cprc-app4-sub 8) : ($code rte oper) > #return(##cprc-app4-sub 9) : ($code rte) 345,346c367,369 < #procedure(##cprc-app-sub 6) < #return(##cprc-app-sub 7) : ($code rte) --- > #return(##cprc-app-sub 6) : ($code rte oper) > #procedure(##cprc-app-sub 7) > #return(##cprc-app-sub 8) : ($code rte) makefile:113: recipe for target 'test1' failed make[1]: [test1] Error 1 (ignored) I don't know whether this is important. Brad On 06/09/2016 02:11 PM, Mikael More wrote: > Awesomeness, thanks!!!!! > > Fantastic, this means tight integration with a functional object > database is possible. > > I guess the expression code is running under the scheduler too, opening > for storage of the database on non-low-latency facilities too, great! > > > > 2016-06-10 1:30 GMT+08:00 Bradley Lucier <lucier(a)math.purdue.edu > <mailto:lucier@math.purdue.edu>>: > > Try adding --enable-auto-forcing to your configure of Gambit. > > > On 06/09/2016 01:20 PM, Adam wrote: > > Hi Marc! > > I have a practical question: > > I am thinking about the possibility of realizing a TIGHTLY > integrated > persistent object store ("object database"). > > (Tightly integrated, that is, with the Scheme heap.) > > The object store would be functional, so the host system can cache > object references as much as it wants. > > > My question is: > > The best thing would be to > > 1) Have lazy loading of objects into the Scheme heap from the > database > (because the stored structures may have wather depth and shape > meaning > that precaching algorithms never would have an idea about what > really > needs to be loaded, so better let the code show that simply > through what > slots etc. it accesses), *AND* to at the same time > > 2) *NOT* need to customize the Scheme code for the lazy loading, > i.e., > have implicit |force| all over the code? > > > A final wish here would be > > 3) The option that the |force| would be run as a procedure > within the > green threading system, so that other green threads would continue > executing while the lazy value is being loaded. Not sure about > this one > though - maybe for code-performance reasons it would be better > to have > it block. > > > Even runtime procedures would need to do the implicit |force|. > So the > values that not are loaded right now, would be represented by a > loading > closure, and the result of closure invocation would be the value > that > should take the place of the respective accessed slot. > > > Can this be done in Gambit, in its current form or with some > very slight > modification? > > Thanks! > > >

3 5

SIGPLAN Programming Languages Mentoring Workshop @ ICFP
by Lindsey Kuper 01 Jui '16

01 Jui '16

SIGPLAN Programming Languages Mentoring Workshop @ ICFP Nara, Japan (co-located with ICFP 2016) Sunday, September 18th, 2016 http://conf.researchr.org/track/icfp-2016/PLMW-ICFP-2016/ We are pleased to invite students interested in functional programming research to the programming languages mentoring workshop at ICFP. The goal of this workshop is to introduce senior undergraduate and early graduate students to research topics in functional programming as well as provide career mentoring advice. We have recruited leaders from the functional programming community to provide overviews of current research topics and give students valuable advice about how to thrive in graduate school, search for a job, and cultivate habits and skills that will help them in research careers. This workshop is part of the activities surrounding ICFP, the International Conference on Functional Programming, and takes place the day before the main conference. One goal of the workshop is to make the ICFP conference more accessible to newcomers and we hope participants will stay through the entire conference. Through the generous donation of our sponsors, we are able to provide travel scholarships to fund student participation. These travel scholarships will cover reasonable travel expenses (airfare and hotel) for attendance at both the workshop and the main three days of the ICFP conference. The workshop is open to all. Students with alternative sources of funding for their travel and registration fees are welcome. In particular, many student attendance programs provide full or partial travel funding for students to attend ICFP 2016, including the ACM Student Research Competition. More information about student attendance programs at ICFP is available: http://conf.researchr.org/home/icfp-2016 Application for Travel Support: The travel funding application is available from the PLMW webpage. The deadline for full consideration of funding is July 1st, 2016. Selected participants will be notified by July 15th. Organizers: Amal Ahmed, Northeastern University Robby Findler, Northwestern University Atsushi Igarashi, Kyoto University

1 0

2nd CfP: SLE 2016 (9th ACM SIGPLAN International Conference on Software Language Engineering)
by Andrei Chis 01 Jui '16

01 Jui '16

**Call for Papers** ======================================================================== 9th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2016) Oct 31-Nov 1, 2016, Amsterdam, Netherlands (Co-located with SPLASH 2016) General chair: Tijs van der Storm, CWI, Netherlands Program co-chairs: Dániel Varro, Budapest University of Technology and Economics, Hungary Emilie Balland, Sensational AG, Switzerland http://conf.researchr.org/track/sle-2016/sle-2016-papers http://www.sleconf.org/2016/ Follow us on twitter: https://twitter.com/sleconf ======================================================================== Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term "software language" is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies). ### Important Dates Fri 17 Jun 2016 - Abstract Submission Fri 24 Jun 2016 - Paper Submission Fri 26 Aug 2016 - Notification Fri 2 Sep 2016 - Artifact submission Fri 16 Sep 2016 - Artifact notification Fri 16 Sep 2016 - Camera ready deadline Mon 31 Oct 09:00 - Tue 1 Nov 18:00 2016 Conference ### Topics of Interest SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in principled engineering approaches and techniques in the following areas: * Language Design and Implementation * Approaches and methodologies for language design * Static semantics (e.g., design rules, well-formedness constraints) * Techniques for behavioral / executable semantics * Generative approaches (incl. code synthesis, compilation) * Meta-languages, meta-tools, language workbenches * Language Validation * Verification and formal methods for languages * Testing techniques for languages * Simulation techniques for languages * Language Integration * Coordination between of heterogeneous languages and tools * Mappings between languages (incl. transformation languages) * Traceability between languages * Deployment of languages to different platforms * Language Maintenance * Software language reuse * Language evolution * Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools * User studies evaluating usability * Performance benchmarks * Industrial applications ### Types of Submissions * **Research papers**: These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages excluding bibliography (in ACM SIGPLAN conference style (http://www.sigplan.org/Resources/Author/)) * **Tool papers**: Because of SLE’s interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages in SIGPLAN proceedings style (see above), with 1 optional additional page for bibliographic references, and a demonstration outline including screenshots of up to 4 pages. Tool demonstrations must have the keywords "Tool Demo" or “Tool Demonstration” in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 4-page demonstration outline will be used by the program committee only for evaluating the submission. ### Artifact evaluation Authors of accepted papers at SLE 2016 are encouraged to submit their experiment results used for underpinning research statements to an artifact evaluation process carried out in early September 2016. This submission is voluntary and will not influence the final decision regarding the papers. Papers that go through the Artifact Evaluation process successfully receive a seal of approval printed on the first page of the paper in the proceedings. Authors of papers with accepted artifacts are encouraged to make these materials publicly available upon publication of the proceedings, by including them as "source materials" in the ACM Digital Library. ### Publications All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers will be published in ACM Digital Library. Authors of distinguished papers from the conference will be invited to revise and submit extended versions of their papers for a Journal special issue. ### Awards * Distinguished paper. Award for most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished reviewer. Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors. ### Program Committee Emilie Balland (co-chair), Sensational AG (SUI) Daniel Varro (co-chair), BME (HUN) Anya Helene Bagge, Univ. Bergen (NOR) Ruth Breu, Univ. Innsbruck (AUT) Jordi Cabot, Univ. Oberta de Catalunya (ESP) Marsha Chechik, Univ. Toronto (CAN) Marcus Denker, INRIA (FRA) Davide Di Ruscio, Univ. L’Aquila (ITA) Martin Erwig, Oregon State Univ. (USA) Bernd Fischer, Stellenbosch University (RSA) Sebastian Gerard, CEA (FRA) Jeremy Gibbons, Oxford Univ. (UK) Holger Giese, Hasso Plattner Inst. (GER) Martin Gogolla, Univ. Bremen (GER) Jeff Gray, Univ. Alabama (USA) Esther Guerra, Autonomous Univ. of Madrid (ESP) Gorel Hedin, Lund Univ. (SWE) Michael Homer, Victoria Univ. Wellington (NZL) Dimitris Kolovos, Univ. York (UK) Ralf Lämmel, Univ. Koblenz (GER) Julia Lawall, LIP6 (FRA) Tihamer Levendovszky, Microsoft (USA) Heather Miller, EPFL (SUI) Pierre-Etienne Moreau, Loria (FRA) Günter Mussbacher, McGill Univ. (CAN) Bruno Oliveira, Univ. of Hong Kong (HKG) Terence Parr, Univ. San Francisco (USA) István Ráth, IncQuery Labs (HUN) Julia Rubin, MIT (USA) Bernhard Schatz, Fortiss (GER) Sibylle Schupp, Univ. Hamburg (GER) Anthony Sloane, Macquarie Univ. (AUS) Emma Söderberg, Google (USA) Eugene Syriani, Univ. Montréal (CAN) Gabi Taentzer, Univ. Marburg (GER) Eric Van Wyk, Univ. Minnesota (USA) Hans Vangheluwe, Univ. Antwerp (BEL) Jurgen Vinju, CWI (NED) Guido Wachsmuth, TU Delft (NED) Eric Walkingshaw, Oregon State Univ. (USA) Andrzej Wąsowski, ITU (DEN) Manuel Wimmer, TU Wien (AUT) Tian Zhang, Nanjing Univ. (CHN)

1 0

Second CFP for Scheme and Functional Programming Workshop 2016
by Alex Shinn 28 Mai '16

28 Mai '16

SECOND NOTICE Call For Presentations 17th Annual Scheme and Functional Programming Workshop WEBSITE: http://scheme2016.snow-fort.org/ LOCATION: Nara, Japan (Co-located with ICFP 2016) DATE: 18 September 2016 ======================================================================== The 2016 Scheme and Functional Programming Workshop is calling for submissions. This year we are accepting general presentation proposals in addition to papers. Submissions related to Scheme, Racket, Clojure, and functional programming are welcome and encouraged. Topics of interest include but are not limited to: Program-development environments, debugging, testing Implementation (interpreters, compilers, tools, benchmarks, etc.) Syntax, macros, hygiene Distributed computing, concurrency, parallelism Probabilistic computing Interoperability with other languages, FFIs Continuations, modules, object systems, types Theory, formal semantics, correctness History, evolution and standardization of Scheme Applications, experience and industrial uses of Scheme Education Scheme pearls (elegant, instructive uses of Scheme) We also welcome submissions related to dynamic or multiparadigmatic languages and programming techniques. ======================================================================== Important Dates: 24 June 2016 - Submissions deadline 22 July 2016 - Author notification 15 August 2016 - Camera-ready deadline 18 September 2016 - Workshop All deadlines are 23:59 (UTC-12, "Anywhere on Earth"). Paper submissions must be in ACM proceedings format, no smaller than 9-point type (10-point type preferred). Microsoft Word and LaTeX templates for this format are available at: http://www.sigplan.org/Resources/Author/ Paper submissions should be in PDF and printable on US Letter, and generally in the range of 6 to 12 pages. Presentation submissions should include an outline of the material. Talks are 40 minutes, including questions and answers. More information available at: http://scheme2016.snow-fort.org/ ======================================================================== Organizers: Alex Shinn (general chair) Kathy Gray (program chair) (Apologies for duplications from cross-posting.)

1 0

gambit github repo moved
by Marc Feeley 27 Mai '16

27 Mai '16

I have just transferred the official repo from the “feeley” github account to the “gambit” organization. Don’t forget to edit .git/config to point to the new location, or you could start from scratch with a git clone https://github.com/gambit/gambit.git The transfer process has automatically moved all issues and also the users of the gitter chat room (which is now at https://gitter.im/gambit/gambit) The URL https://gitter.im/feeley/gambit redirects to https://gitter.im/gambit/gambit, but don’t rely on that for too long. The purpose of the “gambit” organization is to collect in a central location the repositories related to the Gambit system (tools, projects, extensions, modules). If you are interested in creating a repository in the “gambit” organization, please let me know. Marc

1 0