How can I make it work on my local runner and also for forks who cannot use my runner on GitLab.com 2 wth the provided SaaS runners?

If you want to write an awk script, which portable to any awk implementations and versions (gawk/nawk/mawk...) it is really hard, even if with --posix (gawk)

once you have an access token you can use it to make calls from a mobile client, a web browser, or from your server to Facebook's servers. If a token is obtained on a client, you can ship that token down to your server and use it in server-to-server calls. If a token is obtained via a server call, you can also ship that token up to a client and then make the calls from the client.

Any good anti-net programs and Android apps out there? .t3_1301mhl._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #9b9b9b; --postTitleLink-VisitedLinkColor: #9b9b9b; --postBodyLink-VisitedLinkColor: #989898; } I think that I will get an idea of how to go about doing the anti-net note-taking system with an example done by a program. Also with the use of an Android app. Any recommendations for both my phone and my computer? If both of them may be free. Any feedback is welcome.

Yes, you can definitely use a card index for note-taking. In fact, many people find card indexes to be a useful and convenient tool for organizing and storing notes. Here are some tips for using a card index for note-taking:Choose a system: Decide on a system for organizing your cards. You could organize them alphabetically, by topic, by date, or by any other method that works for you.Choose the size of cards: Choose the size of cards that works best for your needs. Common sizes include 3" x 5", 4" x 6", and 5" x 8".Use one card per idea: Write one idea or piece of information on each card. This will help keep your notes organized and easy to reference.Include keywords: Include keywords on each card to make it easier to find relevant information later.Use dividers: Use dividers to separate different topics or sections in your card index. This will help keep your notes organized and easy to navigate.Carry it with you: A card index is a portable tool, so you can take it with you wherever you go. This makes it easy to take notes on the go and to refer to your notes when you need them.Overall, a card index can be a useful and efficient tool for note-taking, especially if you prefer a physical, tangible way of organizing and storing information.

The smaller A6 format, hardlybigger than an ordinary note book sheet, makes it easy everywhere to take short notes forlater sheetification, no matter if one is in a reading room, the tramway or on a train. This is aparticularly valuable characteristic of it!

While the definition of “portable” has changed a lot over the past 40 years, the recognition that technology would uncouple work and location—challenging the foundations and certainties of 20th-century society in the process—has been clear for decades. Every generation has thinkers and tinkerers who dream of connecting seamlessly across borders, locations, and time zones—and some go the extra mile to articulate what that world might look like. 

The European Commission has prepared to legislate to require interoperability, and it calls being able to use your data wherever and whenever you like “multi-homing”. (Not many other people like this term, but it describes something important – the ability for people to move easily between platforms

Reviewing The Original of Laura, Alexander Theroux describes the cards as a “portable strategy that allowed [Nabokov] to compose in the car while his wife drove the devoted lepidopterist on butterfly expeditions.”

Barthes’ use of these cards goes back tohis first readin g of Michelet in 1943, which, as Hollier (2005: 40)notes, is more or less also the time of his very first articles. By 1945,Barthes had already amassed over 1,000 index cards on Michelet’swork alone, which he reportedly transported with him everywhere,from Romania to Egypt (Calvet, 1994: 113).

From my point of view, this approach will help you to write cleaner code. Also, it will help to maintain the project. For instance, moving a file from the current directory to another will cause fewer problems, because every file uses an absolute path instead of a relative one. Last but not least, it helps you during development.

This is not dumb at all. It is exceedingly common to use aliases. It's not about being lazy, it's about writing portable code.

What seems more problematic is divergence between drivers. For example, capybara-webkit and poltergeist support several of the same things. Let's take resizing the window as an example. In capybara-webkit this is page.driver.resize_window(x, y) and in poltergeist it's page.driver.resize(x, y). This means that if a user wants to switch from one to the other they have to change their code. Now I don't know if selenium does or doesn't support resizing the window, but supposing it doesn't I think there's still a lot of value in the capybara project deciding what the blessed API is, because then all the drivers that support that feature can implement it using the same API, increasing portability.

This demonstrates how the nature of node_modules resolution allows for workspaces to enable a portable workflow for requiring each workspace in such a way that is also easy to publish these nested workspaces to be consumed elsewhere.

Different ways to prepend a line: (echo 'line to prepend';cat file)|sponge file sed -i '1iline to prepend' file # GNU sed -i '' $'1i\\\nline to prepend\n' file # BSD printf %s\\n 0a 'line to prepend' . w|ed -s file perl -pi -e 'print"line to prepend\n"if$.==1' file

For filter-branch, using pipelines like git ls-files | grep -v ... | xargs -r git rm might be a reasonable workaround but can get unwieldy and isn't as straightforward for users; plus those commands are often operating-system specific (can you spot the GNUism in the snippet I provided?)

I just wanted to point out that the syntax is not supported by the POSIX standard and thus won't universally work in /bin/sh scripts (many people erroneously use bash syntax in /bin/sh scripts)

does not use TCL, Perl, PHP, Python or anything else as an underlying language is written entirely in C has small and simple source code can easily be ported to almost all UNIX-like systems

you can use "${@:1}" instead of shift, but that requires bash instead of sh in your #! shebang. IMHO your original shift approach is simpler and better

xdg-open should do the same thing - actually, it will call gnome-open, or kde-open, or whatever, depending on your desktop environment. Thus it's more portable.

Now this probably won't make difference in the real world (e.g. because the exit codes are not portable and on top of that not always unambiguous as discussed in Default exit code when process is terminated?)

In any case signal handling in shells is one of the least reliable and portable aspects. You'll find behaviours vary greatly between shells and often between different versions of a same shell. Be prepared for some serious hair pulling and head scratching if you're going to try to do anything non-trivial.

Portable... your .name address works with any email or web service. With our automatic forwarding service on third level domains, you can change email accounts, your ISP, or your job without changing your email address. Any mail sent to your .name address arrives in any email box you choose.

Flexibility: your solution can be ported to other UI's, or you can replace your favourite state management form library without affecting your validation engine.

How to Export Your Content If you log into Graphite before August 15th, you can download each file in any of the available formats offered. If you'd like a bulk download, I recommend (for the technically inclined) using the exporter tool I created. For those less technically inclined, Blockstack may have some options for you. Remember, Graphite never owned your content. Never had control of your content. And that was the real power of its offering. 

easy access/edit/backup and then restore saved data using the integrated Bookmark Manager (even on smartphone / tablet) even if the addon is not installed

Now personal data exports include users session information and users location data from the community events widget. Plus, a table of contents!See progress as you process export and erasure requests through the privacy tools.

But it also requires that you keep personal data well-organized and accessible to those who require access to it.

The right to data portability Under certain conditions, users have the right to obtain (in a machine-readable format) and use their personal data for their own purposes.

data liberation is best provided through APIs, and data portability is best provided by building code using those APIs to perform cloud-to-cloud migration

The data liberation effort focuses specifically on data that could hinder users from switching to another service or competing product—that is, data that users create in or import into Google products

At Google, our attitude has always been that users should be able to control the data they store in any of our products, and that means that they should be able to get their data out of any product. Period. There should be no additional monetary cost to do so, and perhaps most importantly, the amount of effort required to get the data out should be constant, regardless of the amount of data. Individually downloading a dozen photos is no big inconvenience, but what if a user had to download 5,000 photos, one at a time, to get them out of an application? That could take weeks of their time.

Want to keep your users? Just make it easy for them to leave.

The second way we avoid locking you into 1Password is through the ability to export data to a more neutral format. Not all versions are yet where we want them to be with respect to export, and we’re working on that. But there is usually some path, if not always a simple click away, to export your 1Password data.

Users have the right to obtain (in a machine readable format) their personal data for the purpose of transferring it from one controller to another, without being prevented from doing so by the data processor.

The Right to access is closely linked to the Right to data portability, but these two rights are not the same.

Export and migrate your data between hosting options at any time