- Pharo-users - lists.pharo.org

Re: [Pharo-users] Read and parse maildir (offlineimap) files

by Alistair Grant

Hi CÃ©drick, On Fri, 8 Mar 2019 at 16:12, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > Hi Alistair, > > This looks like what Iâd like to have (parsing emails). Iâd better like an IMAP Client but using offlinmap might be an option. > > Will look at it. > > Do you have an exemple of milder format files ? Attached is the email you sent. I found https://github.com/codeZeilen/SMailDir but it is written for Squeak and doesn't load cleanly in Pharo (I haven't actually done anything with it yet). Cheers, Alistair > > Le 8 mars 2019 Ã 15:49, Alistair Grant <akgrant0710(a)gmail.com> a Ã©crit : > > > > Hi Everyone, > > > > I'd like to be able to parse and read the mail files as saved by > > offlineimap, i.e. in maildir format (one message per file). > > > > Does anyone know of any existing libraries in Pharo? > > > > Thanks very much, > > Alistair > > > >

March 8, 2019

Re: [Pharo-users] Read and parse maildir (offlineimap) files

by CÃ©drick BÃ©ler

Hi Alistair, This looks like what Iâd like to have (parsing emails). Iâd better like an IMAP Client but using offlinmap might be an option. Will look at it. Do you have an exemple of milder format files ? Cheers, CÃ©drick > Le 8 mars 2019 Ã 15:49, Alistair Grant <akgrant0710(a)gmail.com> a Ã©crit : > > Hi Everyone, > > I'd like to be able to parse and read the mail files as saved by > offlineimap, i.e. in maildir format (one message per file). > > Does anyone know of any existing libraries in Pharo? > > Thanks very much, > Alistair >

March 8, 2019

Re: [Pharo-users] ldap, Pier3 & git migration

by Albrecht Baur

sorry for double posting in dev and users ... I pushed it to https://github.com/pharo-contributions/LDAP There it fits better (and we have the 'pharo' at least inside the path...) Best Albrecht On 08.03.19 15:05, Esteban Maringolo wrote: > I wasn't aware of LDAP support in Pharo. Thanks for porting it. > > Wouldn't it be better to call the repo "pharo-ldap"? > > When my repositories are Pharo specific and don't have a fancy project > name I name them "pharo-something", e.g. "pharo-couchdb", > "pharo-base58", "pharo-bip39mnemonic", etc. > > Regards, > > Esteban A. Maringolo > > > El vie., 8 mar. 2019 a las 8:45, Albrecht Baur via Pharo-users > (<pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>>) > escribiÃ³: > > Hi, In case someone can use it: I used Peters git migration tool > for ... > http://smalltalkhub.com/#!/~PharoExtras/LDAP/ > ... and put it to: > https://github.com/a2b-alb/PharoExtras-LDAP > > I don't know if this is the right place or if you would rather > have it > under ... > https://github.com/pharo-contributions/ > ... or somewhere else. > > ------------- here the question: > I started trying to do the same migration process for ... > http://www.smalltalkhub.com/#!/~Pier/Pier3 > ... but I failed on errors loading older mcz files: > > "instance of ByteString did not understand #peek" > on: MCMczReader >> contentsForMember: > (ZnInvalidUTF8: Illegal leading byte for utf-8 encoding) > > Is this wrong encoding or corrupted files ? > How to treat these files ? -> Is just ignoring this majority of > failing > mcz files via migration ignoredFileNames: #() > ok ? > > ------------- > As a workaround I then left the history versions behind and took only > the newest mcz files. But I am not sure which package version "is in > harmony" with the other ones...Â ;-) > -> While trying out which versions of the ConfigurationOfPier3 > load in a > p7 image only the #stable one loaded without problems. The newer ones > didn't. > > I did this by first loading as much pier3 dependencies (seaside, > magritte, ...) from the new github repos. So I can then say ... > onConflict: [ :e | e useLoaded ]; > ... when loading pier3 from smaltalkhub. > > Can someone who knows pier3 better than me, give me a hint on which > package versions combinations are the ones to go with ? > -> Is to just start with the newest mcz files the way to go? Or > should I > use the #stable ConfigurationOfPier3 ? > > best, > Albrecht > >

March 8, 2019

Read and parse maildir (offlineimap) files

by Alistair Grant

Hi Everyone, I'd like to be able to parse and read the mail files as saved by offlineimap, i.e. in maildir format (one message per file). Does anyone know of any existing libraries in Pharo? Thanks very much, Alistair

March 8, 2019

Re: [Pharo-users] ldap, Pier3 & git migration

by Esteban Maringolo

I wasn't aware of LDAP support in Pharo. Thanks for porting it. Wouldn't it be better to call the repo "pharo-ldap"? When my repositories are Pharo specific and don't have a fancy project name I name them "pharo-something", e.g. "pharo-couchdb", "pharo-base58", "pharo-bip39mnemonic", etc. Regards, Esteban A. Maringolo El vie., 8 mar. 2019 a las 8:45, Albrecht Baur via Pharo-users (< pharo-users(a)lists.pharo.org>) escribiÃ³: > Hi, In case someone can use it: I used Peters git migration tool for ... > http://smalltalkhub.com/#!/~PharoExtras/LDAP/ > ... and put it to: > https://github.com/a2b-alb/PharoExtras-LDAP > > I don't know if this is the right place or if you would rather have it > under ... > https://github.com/pharo-contributions/ > ... or somewhere else. > > ------------- here the question: > I started trying to do the same migration process for ... > http://www.smalltalkhub.com/#!/~Pier/Pier3 > ... but I failed on errors loading older mcz files: > > "instance of ByteString did not understand #peek" > on: MCMczReader >> contentsForMember: > (ZnInvalidUTF8: Illegal leading byte for utf-8 encoding) > > Is this wrong encoding or corrupted files ? > How to treat these files ? -> Is just ignoring this majority of failing > mcz files via migration ignoredFileNames: #() > ok ? > > ------------- > As a workaround I then left the history versions behind and took only > the newest mcz files. But I am not sure which package version "is in > harmony" with the other ones... ;-) > -> While trying out which versions of the ConfigurationOfPier3 load in a > p7 image only the #stable one loaded without problems. The newer ones > didn't. > > I did this by first loading as much pier3 dependencies (seaside, > magritte, ...) from the new github repos. So I can then say ... > onConflict: [ :e | e useLoaded ]; > ... when loading pier3 from smaltalkhub. > > Can someone who knows pier3 better than me, give me a hint on which > package versions combinations are the ones to go with ? > -> Is to just start with the newest mcz files the way to go? Or should I > use the #stable ConfigurationOfPier3 ? > > best, > Albrecht > > >

March 8, 2019

Re: [Pharo-users] The best way to construct a file/url path handling misplaced $/ chars

by Esteban Maringolo

I don't know whether you want to build just "paths" or valid URIs, if it's the latter, I'd suggest ZnUrl as well. '/name/' asPath / 'resource'. -> /name/resource '/name/' asPath / '/resource'. -> /resource (which is correct) '/name/' asUrl / '/resource' -> /name//resource (which is correct as well). The other way is to use path segments, as CÃ©drick suggested. Regards, Esteban A. Maringolo El vie., 8 mar. 2019 a las 8:34, Tim Mackinnon (<tim(a)testit.works>) escribiÃ³: > Iâm sure we have something in the image that deals with this - but if > writing a generic http retriever and wanting to correctly cope with > constructing resource paths where the base path may or may not have a > trailing /, and the resource path may or may not have a leading / > > Basically - magically handle > > /name//resourse > /name///resource > > > Iâm sure we have something simple - the best I could see was to abuse Path > like: > > (Path from: basePath, '/', resourcePath) pathString > > Is this a good way to do it? > > Tim >

March 8, 2019

What is the pharo days code?

by Tim Mackinnon

Anyone know what is my code to use for Pharo Days registration? I got my member confirmation but have no idea what the code is all about that it wants for the Pharo days registration? (I recall this happening a few years ago but didnât pay attention) Any ideas? Tim

March 8, 2019

Re: [Pharo-users] The best way to construct a file/url path handling misplaced $/ chars

by CÃ©drick BÃ©ler

'/foo//' copyWithoutAll: '/' > Le 8 mars 2019 Ã 12:40, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > > Not sure but I would use ZnUrl > > ZnUrl new > scheme: #http; > host: NetNameResolver loopBackName; > addPathSegments: #('echo' 'foo'); > yourself > > Making sure Path segments do not contain separatorâ¦ > > Hth, > > CÃ©drick > > > >> Le 8 mars 2019 Ã 12:33, Tim Mackinnon <tim(a)testit.works> a Ã©crit : >> >> Iâm sure we have something in the image that deals with this - but if writing a generic http retriever and wanting to correctly cope with constructing resource paths where the base path may or may not have a trailing /, and the resource path may or may not have a leading / >> >> Basically - magically handle >> >> /name//resourse >> /name///resource >> >> >> Iâm sure we have something simple - the best I could see was to abuse Path like: >> >> (Path from: basePath, '/', resourcePath) pathString >> >> Is this a good way to do it? >> >> Tim >

March 8, 2019

Re: [Pharo-users] The best way to construct a file/url path handling misplaced $/ chars

by CÃ©drick BÃ©ler

Not sure but I would use ZnUrl ZnUrl new scheme: #http; host: NetNameResolver loopBackName; addPathSegments: #('echo' 'foo'); yourself Making sure Path segments do not contain separatorâ¦ Hth, CÃ©drick > Le 8 mars 2019 Ã 12:33, Tim Mackinnon <tim(a)testit.works> a Ã©crit : > > Iâm sure we have something in the image that deals with this - but if writing a generic http retriever and wanting to correctly cope with constructing resource paths where the base path may or may not have a trailing /, and the resource path may or may not have a leading / > > Basically - magically handle > > /name//resourse > /name///resource > > > Iâm sure we have something simple - the best I could see was to abuse Path like: > > (Path from: basePath, '/', resourcePath) pathString > > Is this a good way to do it? > > Tim

March 8, 2019

The best way to construct a file/url path handling misplaced $/ chars

by Tim Mackinnon

Iâm sure we have something in the image that deals with this - but if writing a generic http retriever and wanting to correctly cope with constructing resource paths where the base path may or may not have a trailing /, and the resource path may or may not have a leading / Basically - magically handle /name//resourse /name///resource Iâm sure we have something simple - the best I could see was to abuse Path like: (Path from: basePath, '/', resourcePath) pathString Is this a good way to do it? Tim

March 8, 2019