{"@attributes":{"version":"2.0"},"channel":{"title":"DEV Community: Mathieu PATUREL","description":"The latest articles on DEV Community by Mathieu PATUREL (@math2001).","link":"https:\/\/dev.to\/math2001","image":{"url":"https:\/\/media2.dev.to\/dynamic\/image\/width=90,height=90,fit=cover,gravity=auto,format=auto\/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F17319%2F36a49a5c-76ea-48ff-9e67-e18e143057ad.png","title":"DEV Community: Mathieu PATUREL","link":"https:\/\/dev.to\/math2001"},"language":"en","item":[{"title":"Can you translate it back?","pubDate":"Sat, 26 May 2018 00:50:17 +0000","link":"https:\/\/dev.to\/math2001\/can-you-translate-it-back-3327","guid":"https:\/\/dev.to\/math2001\/can-you-translate-it-back-3327","description":"<p>I've got a little challenge for you.<\/p>\n\n<div class=\"highlight js-code-highlight\">\n<pre class=\"highlight plaintext\"><code>ib jb eikybfi eite hvim\n<\/code><\/pre>\n\n<\/div>\n\n<p>Can you translate this encrypted text back to its original form?<\/p>\n\n<p>If you do, send me an email at <a href=\"\/\/mailto:math2001.contact@protonmail.com\">math2001.contact@protonmail.com<\/a> explaining how you found it, and I'll add you to the glorious list of people who found the solution \ud83d\ude04 (see below).<\/p>\n\n<h3>\n  \n  \n  Rules\n<\/h3>\n\n<p>I guarantee you the original message:<\/p>\n\n<ul>\n<li>contains only lower case ASCII letters (<code>abcdefghijklmnopqrstuvwxyz<\/code>)<\/li>\n<li>has the same spaces as in the encrypted message. So you know that the first     word will have 2 letters, the second one as well, the third one 7, etc...<\/li>\n<li>can only translated to one string (the one I gave you)<\/li>\n<\/ul>\n\n<h3>\n  \n  \n  They found it!\n<\/h3>\n\n<blockquote>\n<p>The glorious and amazing people who had a crack and found the secret message!<\/p>\n<\/blockquote>\n\n<p>The list is <a href=\"https:\/\/math2001.github.io\/post\/challenge-1-translate-back#they-found-it\">over here<\/a>.<\/p>\n\n<h3>\n  \n  \n  Solution\n<\/h3>\n\n<p>Hey hey. Smart one, looking at the right place, \ud83d\ude04<\/p>\n\n<p>I'll be posting the original message, as well as an explanation about how it worked on <a href=\"https:\/\/math2001.github.io\">my blog<\/a> next week, that is the <strong>Friday 1 June 2018<\/strong>.<\/p>\n\n","category":["challenge","cipher"]},{"title":"Display a file from another branch","pubDate":"Wed, 16 May 2018 07:07:41 +0000","link":"https:\/\/dev.to\/math2001\/display-a-file-from-another-branch-1efp","guid":"https:\/\/dev.to\/math2001\/display-a-file-from-another-branch-1efp","description":"<p>Ever wanted to see a file from a different branch? Well, no need to <code>stash<\/code> &amp;&amp; <code>checkout<\/code>, just use <code>git show<\/code>.<br>\n<\/p>\n\n<div class=\"highlight js-code-highlight\">\n<pre class=\"highlight plaintext\"><code>dev $ git show master:path\/to\/file\n<\/code><\/pre>\n\n<\/div>\n\n\n\n<p>PS: this works with any reference (not sure if that's the right term, correct me if I'm wrong), like commit and tags:<br>\n<\/p>\n\n<div class=\"highlight js-code-highlight\">\n<pre class=\"highlight plaintext\"><code>master $ git log --oneline\nd529def Some more new stuff\n4598db3 Some new stuff\ne8dd680 init\nmaster $ git show e8dd680:path\/to\/file\n&lt;The content of the file at commit e8dd680&gt;\n<\/code><\/pre>\n\n<\/div>\n\n\n\n<p>Enjoy!<\/p>\n\n","category":["git","quicktip","tip"]},{"title":"Combine your SVGs","pubDate":"Thu, 12 Oct 2017 08:30:41 +0000","link":"https:\/\/dev.to\/math2001\/combine-your-svgs-35d","guid":"https:\/\/dev.to\/math2001\/combine-your-svgs-35d","description":"<p>SVG images are awesome, I absolutely love it (and who doesn't). A great thing about them is that you can combine them very easily, and use integrate them <em>into<\/em> your web page in single line. <\/p>\n\n<p>It makes your website faster since you only make one HTTP request instead of .<\/p>\n\n<p>A quick read about how to do that over at <a href=\"https:\/\/math2001.github.io\/post\/combine-svgs\/\">math2001.github.io\/post\/combine-svgs<\/a><\/p>\n\n","category":["svg","performances","web"]},{"title":"Which editors do you use?","pubDate":"Sat, 07 Oct 2017 07:11:46 +0000","link":"https:\/\/dev.to\/math2001\/which-editors-do-you-use-bgg","guid":"https:\/\/dev.to\/math2001\/which-editors-do-you-use-bgg","description":"<p>The question's in the title. Here's my answer: <strong>VIM<\/strong> and <strong>Sublime Text<\/strong><\/p>\n\n<p>Sublime text is better than vim except for the fact that it doesn't support fully (yet) VIM mappings (and plugins, but I could deal with this). I use the <code>Six<\/code> package, a python emulation of VIM (ST plugins are written in Python).<\/p>\n\n<p>ST is absolutely beautiful, amazingly fast, supports proper project management (settings per project for example), a proper multi cursor (not a hack like vim-multiple-cursor), great syntax highlighting (engine and rules), and <em>much<\/em> more...<\/p>\n\n<p>Despite all these advantages, I'm still using the actual VIM, sometimes giving another go at ST (like right now).<\/p>\n\n<p>That's it! Your turn!<\/p>\n\n","category":["editor","discuss"]},{"title":"Share on dev.to?","pubDate":"Tue, 26 Sep 2017 21:39:39 +0000","link":"https:\/\/dev.to\/math2001\/share-on-devto-64m","guid":"https:\/\/dev.to\/math2001\/share-on-devto-64m","description":"<p>I'm currently building my blog (over at <a href=\"http:\/\/math2001.github.io\">math2001.github.io<\/a> if you're intersted), and I'm putting some link to share the current posts (twitter, etc).<\/p>\n\n<p>And I was wondering if dev.to was an appropriate link to use... I'm quite new to this blazing fast website ( \u00f0\u0178\u02dc\u008d ), so, I was wondering: is dev.to only for sharing \"new\" content, or we can share existing stuff. I feel like the second option, but again, I'm new.<\/p>\n\n<p>Basically, I'm asking if a link saying \"Share on dev.to\" would be appropriate.<\/p>\n\n<p>What do you guys think?<\/p>\n\n","category":["question","meta","discuss"]},{"title":"List files in any branch in git","pubDate":"Mon, 25 Sep 2017 00:57:54 +0000","link":"https:\/\/dev.to\/math2001\/list-files-in-any-branch-in-git","guid":"https:\/\/dev.to\/math2001\/list-files-in-any-branch-in-git","description":"<h2>\n  \n  \n  List entire branch content\n<\/h2>\n\n\n\n<div class=\"highlight js-code-highlight\">\n<pre class=\"highlight plaintext\"><code>~\/my\/repo $ git ls-tree mybranch -r --name-only\n.gitignore\nLICENSE\nREADME.md\ncli.js\ndemo.gif\nindex.html\nlive-svg.svg\npackage.json\nserver.js\ntests\/cli.js\n<\/code><\/pre>\n\n<\/div>\n\n\n\n<h2>\n  \n  \n  List only one folder's content\n<\/h2>\n\n<p>You don't need <code>grep<\/code>!<br>\n<\/p>\n\n<div class=\"highlight js-code-highlight\">\n<pre class=\"highlight plaintext\"><code>~\/my\/repo $ git ls-tree mybranch:test -r --name-only\ntests\/cli.js\n<\/code><\/pre>\n\n<\/div>\n\n\n\n<p>More informations about <a href=\"https:\/\/git-scm.com\/docs\/git-ls-tree\">git ls-tree<\/a>.<\/p>\n\n<p>Hope it'll save you some time! \u00f0\u0178\u02dc\u0153<\/p>\n\n","category":["git","tip"]},{"title":"Programmatically get current git branch","pubDate":"Sun, 24 Sep 2017 07:28:19 +0000","link":"https:\/\/dev.to\/math2001\/programmatically-get-current-git-branch","guid":"https:\/\/dev.to\/math2001\/programmatically-get-current-git-branch","description":"<p>Nice and easy. Works with git 1.6.3 and higher.<br>\n<\/p>\n\n<div class=\"highlight js-code-highlight\">\n<pre class=\"highlight shell\"><code><span class=\"nv\">$ <\/span>git rev-parse <span class=\"nt\">--abbrev-ref<\/span> HEAD\nmaster\n<\/code><\/pre>\n\n<\/div>\n\n\n\n","category":["git","bash","branch","ps1"]}]}}