File format matters. Here’s the reliability ranking for how well AI reads different formats:.txt / .md — Minimal noise, clear structure (best)JSON / CSV — Great for structured dataDOCX — Fine if formatting is simpleDigital PDFs — Extraction can mix headers, footers, columnsPPTX — Text order can be unpredictableScanned PDFs / images — Worst; requires OCR, highly error-prone

one morning, with the errant press of a button, I overwrote the file that had contained my work and weeks of toil were simply obliterated. Not a catastrophic fire or an explosion, but the innocent stroke of a key had annihilated what I had previously put so much of myself into for so many days. This led me to radically doubt the weight of that work.

I use dashes -, for the reasons you mention above. I avoid underscores because they require using the shift key, so take at least twice as long to type (also, I think they're ugly)

With so many characters that you might not think should be special, in fact being special, I just use the special characters anyway. This also puts me in the good habits of using bash completion, where it will auto-escape all the special characters in a filename. But it also puts me in the good habits of escaping/quoting EVERYTHING in scripts and multi-part 1-liners in bash. For example, in just a simple 1-liner: for file in *.txt; do something.sh "$file"; done That way, even if one of the files has a space, or some other character, the do part of the loop will still act on it, and not miss on 2 or more file-name-parts, possibly causing unintended side-effects. Since I cannot control the space/not-space naming of EVERY file I encounter, and if I tried, it would probably break some symlinks somewhere, causing yet more unintended consequences, I just expect that all filename/directoryname could have spaces in it, and just quote/escape all variables to compensate. So, then I just use whatever characters I want (often spaces) in filenames. I even use spaces in ZFS dataset names, which I have to admit has caused a fair amount of head-scratching among the developers that write the software for the NAS I use. Sum-up: Spaces are not an invalid character, so there's no reason not to use them.

Some applications and computer scripts may not recognize spaces or will process your files differently when using spaces. A best practice is to replace spaces in file names with  an underline (_) or hyphen (-).

I've noticed somethings, particularly ADB commands, use spaces to issue the next part of the command. Thus having a space would say that there's a new command. And since hyphens are actually used in some spelling, such as my last name, it's better to use underscores.

I didn't see this mentioned, but lots of software doesn't treat the underscore as a word separator (also called a "break character") these days. In other words, you can't jump to next word with Ctrl+Right-arrow or select individual words by double-clicking on them. The argument is that variable names in some programming languages like Python use snake_case, so highlighting them might require an extra Ctrl+Right-arrow. I do not necessarily like that decision, because, while being (marginally) useful in those limited domains, it makes file renaming and any other word manipulations or typesetting very cumbersome.

But one thing to remember is that if you are primarily doing python coding - and your code tree has files/directories with hyphen in them and you intend to use them as modules (do an import filename in your code), then this will cause errors as python modules cannot have hyphen in them.

Underscores are usually the convention that people use when replacing spaces, although hyphens are fine too I'd say. But since hyphens might show up in other ways such as hyphenated words, you'll have more success in preserving a name value by using underscores. For instance, if you have a file called "A picture taken in Winston-Salem, NC.jpg" and you want to convert the spaces to underscores, then you can preserve the hyphen in the name and retain its meaning.

"we [Google] don't really care about underscore versus dashes."

I must be the exception, because I use both spaces and underscores, depending on circumstances.   The practical/obsessive-compulsive side of me saves all my documents using spaces. They're cleaner to read than underscores, and they look far more professional.   The programmer side of me still uses underscores in files that will be accessible via the web or that need to be parsed in a program.   And to complicate matters worse, I use camel case to name all my programming files. So in actuality I use 3 standards interchangeably.   Both have their uses, I just choose one for clarity and one for ease of use.

Separating each of these entities with a hyphen allows you to double-click and highlight only that entity. With underscores-only, you need to enlist the painstaking process of precisely positioning your cursor at the beginning of the entity, then dragging your blue selector to the end of the entity.

Getting the data

the real problem is what we're layering the web on we shouldn't be doing the web over this kind of just simple file distribution system that works over TCP and you have to work really hard to put over anything else we should be putting the web over a distribution system that can deal with the distributed case that is offline first and uh this is are kind of like stats showing the usage of mobile apps versus uh the web and so on so this is a very real real thing

Utopia is a content-centric web application platform. It leverages the file-system to provide a mapping between logical resources and files on disk.

while true; do waitforsave assignment.ly; lily assignment.ly; say "done"; done

file transfers

OK, remember how, in several of my past issues, I've kept at you to create a "swipe file" of good ads, sales letters and so on? Not to mention all those headline cards? You do remember? Good!

From an organizational standpoint, the beauty of sermons is that each revolves around a specific theme. Accordingly, King could devote a single folder to each topic. He accumulated 166 folders, each with a title like “Loving your Enemies” (folder 1), “Why the Christian must Oppose Segregation” (folder 87), “Mental Slavery” (folder 113), and “The Misuse of Prayer” (folder 166). These folders contain King’s outlines; source material, like clippings from books; and drafts.

То, что мы будем называть Черным лебедем (с большой буквы), — это событие, обладающее следующими тремя характеристиками.

the modern textual archive format

Causal Deep Learning Authors:Jeroen Berrevoets, Krzysztof Kacprzyk, Zhaozhi Qian, Mihaela van der Schaar

Comedian Phyllis Diller had “gag file,” which is now housed at The Smithsonian: Phyllis Diller’s groundbreaking career as a stand-up comic spanned almost 50 years. Throughout her career she used a gag file to organize her material. Diller’s gag file consists of a steel cabinet with 48 drawers (along with a 3 drawer expansion) containing over 52,000 3-by-5 inch index cards, each holding a typewritten joke or gag.

Hanna BredenbeckCorp is a project assistant in the Division of Culture and the Arts.

In the end, I numbered and scanned 52,569 individual note cards from the Phyllis Diller gag file.

This joke card has a comic clipped from a newspaper glued to it. During the digitization process, the index card was put in a clear Mylar sleeve to prevent the comic, with its brittle glue, from being damaged or separated from the card.

While most of the joke cards are simply index cards with a joke typed on, others are more complicated. Some cards have strips of paper glued to them with longer jokes on those papers. Some cards have entire letter-size sheets of paper containing long jokes stapled to the cards. Some cards have comic strips, cut from the newspaper, glued to the cards. Other cards are not even cards but are just pieces of printer paper with jokes scribbled on them. These irregular cards were not stable enough to be sent through the feed scanner and had to be scanned one-by-one using a flatbed scanner, which slowed my progress.

I started my project by writing a small number, in pencil, on the back of each card. The numbers are used to keep track of the original drawer in which the card was located, as well as the card's position within that drawer. For example, the card numbered 15-0837 would be the 837th card in Drawer 15.

Oliar, Dotan; Sprigman, Christopher (2008). "There's No Free Laugh (Anymore): The Emergence of Intellectual Property Norms and the Transformation of Stand-Up Comedy". Virginia Law Review. 94 (8): 1848. JSTOR 25470605. Retrieved September 16, 2020. There is also evidence in the [Diller archive…at the Smithsonian in Washington, D.C.] file suggesting that Diller appropriated from other sources [apart from self-creation or using her writing team], including newspaper comic strips and comedy books. For example, a number of Diller's jokes about her dysfunctional marriage to her fictional husband 'Fang' appear to have been inspired by a comic strip, 'The Lockhorns,' that Diller followed obsessively over the course of nearly a decade. The Diller joke files contain hundreds of 'Lockhorns' panels cut out of newspapers and mounted on index cards.

"The [joke] file is like a tree," says Diller. "Leaves drop off, and new leaves are added—the new stuff pushes out the old." Along with this cache—Diller refers to it as "my life in one-liners"

Even the alphabetized categories evoke a laugh: "Science, Seasons, Secretary, Senile, Sex, Sex Symbols, Sex Harassment, Shoes, Shopping..." "Food Gripes, Foreign (incidents & personalities), Foundations (bra & underwear), Fractured Speech, Freeways, Friends, Frugality, Frustrations, Funerals, Funny Names..."

a steel filing cabinet of safe-like dimensions

“The file is like a tree,” Diller told the magazine’s Owen Edwards in 2007. “Leaves drop off, and new leaves are added—the new stuff pushes out the old.”

each typed on an index card and filed under such prophetic taglines as “Science, Seasons, Secretary, Senile, Sex, Sex Symbols, Sex Harassment, Shoes, Shopping…” and “Food Gripes, Foreign (incidents & personalities), Foundations (bra & underwear), Fractured Speech, Freeways, Friends, Frugality, Frustrations, Funerals, Funny Names…”

This beige metal cabinet is Phyllis Diller’s gag file, a categorized archive of the jokes Diller used in her stand-up comedy routines throughout her half-century long career. A small three drawer expansion of the gag file is also in NMAH’s collection (Catalog Number 2003.0289.01.02). The 48 drawers of the gag file, along with the 3 drawer expansion, contain a total of 52,569 3-by-5 inch index cards, each holding a typewritten joke or gag.

Phyllis Diller Gag File - Drawer No. 49, Part 1

Numbers on Cards The curatorial and collections teams are trying to learn more about the appearance of "No. #" on cards. Please transcribe this number on a separate line underneath the Date line, above the Joke line.

The digitization of Phyllis Diller’s index card collection was generously supported by Mike Wilkins and Sheila Duignan.

48 drawers (along with a 3 drawer expansion)

Photo: Hugh Talman, Smithsonian's National Museum of American History

Photo: Hugh Talman, Smithsonian's National Museum of American History.

on Aug. 12, the National Museum of American History is giving the artifact pristine treatment.WpGet the full experience.Choose your planArrowRight"Have You Heard the One . . . ? The Phyllis Diller Gag File" is an exhibition of the beige cabinet in the quiet Albert H. Small Documents Gallery.

Diller typed her jokes on index cards and filled 48 file drawers.

Most of the gags, written from the 1960s to the 1980s, are just like that—one per card. But a few that are more involved sometimes take a few cards to tell.

Most of the gags, written from the 1960s to the 1980s

But when Diller’s jokes came up for transcription last week, “they are going like gangbusters,” says Meghan Ferriter, project coordinator. “I think we actually gained about 115 new volunteers in one day.”

They were typed and meticulously filed into 48 drawers of a large, beige Steelmaster cabinet on wheels that she donated, along with a few of her wilder getups and wigs to the Smithsonian in 2003—less than a decade before her death in 2012 at 95.

SIMON: That's Heidi Rotbart, Phyllis Diller's longtime friend and producer. That gag file, as Phyllis Diller called it, is a piece of history, a hefty taupe filing cabinet filled with 53,000 alphabetized jokes.

HEIDI ROTBART: She would write a joke on a piece of paper, and her assistants would type them up on 3-by-5 cards and then place them in the joke file.

Three weeks and 52,569 jokes later, the job was completed.

Three weeks and 52,569 jokes later, the job was completed.

The joke file is a snapshot of American history.”

“I admire her ability for organization too. My jokes are still mostly in my head. She got hers on paper in alphabetical order.

Another important 20th-century thinker to rely on index cards was pioneering media theo-rist Harold Innis.18 The executors of his estate published a tome called The Idea File (1980),composed of 18 inches of index cards, plus five inches of reference cards. Innis had a selection ofhand-written index cards typed up and numbered, 1 through 339. It is unclear if these rumina-tions on television and art, communication and trade, secrecy and money, literature and the oraltradition, archives and history were intended to constitute a book project; the decision to publishthe cards balances the putative will to posterity of an author, and the potential embarrassmentof incomplete work. Clearly Innis intended to work synchronically rather than diachronically,to focus less on logical connections than on analogies, to practice pattern recognition—andthe associative links of a card index lend themselves perfectly to this kind of project.

he Automatic File & Index Co.

debían estarprotagonizados por extranjeros y tratar de cosas con las que no podía identificarme. Puesbien, la situación cambió cuando descubrí los libros africanos.No había muchos disponibles, y no eran tan fáciles de encontrar como los extranjeros.Pero gracias a escritores como Chinua Achebe y Camara Laye, mi percepción de laliteratura cambió. Comprendí que en la literatura también podía existir gente como yo,chicas con la piel de color chocolate cuyo pelo rizado no caía en colas de caballo.Empecé a escribir sobre asuntos que reconocía.5

The ID suffix was added because I use external tools to add notes to my vault so I needed a means to ensure there would never be a collision. For example, Alfred. If I accidentally typed the name of a note that already exists into it I didn’t want it to accidentally overwrite an existing note,

Use the Get-ChildItem cmdlet with the -Recurse switch: Get-ChildItem -Path V:\Myfolder -Filter CopyForbuild.bat -Recurse -ErrorAction SilentlyContinue -Force

Template: <%* const id = tp.file.creation_date("YYYYMMDDHHmmss"); await tp.file.rename(`${id} ${tp.file.title}`); %>

Current ruby releases generate *.tar.gz, *.tar.bz2, *.tar.xz, and *.zip. But I think we can stop generating *.tar.bz2. I think *.tar.bz2 are less merit. For better size, *.tar.xz exist. For better compatibility, *.tar.gz and *.zip exist.

There are also some advantages to a multi-file YAML format OpenAPI definition: Reuse schema objects to keep things DRY (don't repeat yourself) Smaller diffs compared to JSON (especially for markdown descriptions) Easier to navigate Easier to edit with confidence

Process the log file to determine the spread of data: cat /tmp/sslparams.log | cut -d ' ' -f 2,2 | sort | uniq -c | sort -rn | perl -ane 'printf "%30s %s\n", $F[1], "="x$F[0];'

doesn't know if .env is a hidden file with no extension or a *.env without a filename.

If you do not have an iOS device or a machine running OS X to open your IMOVIEMOBILE file, you can still access its contents. First, copy the IMOVIEMOBILE file, rename the file extension to "zip", decompress the file, and the project content will be in a folder called "Assets." You can then open the original content in a video editing program.

As powerful as search can be, studies5 have found that in manysituations people strongly prefer to navigate their file systemsmanually, scanning for the information they’re looking for. Manualnavigation gives people control over how they navigate, with foldersand file names providing small contextual clues about where to looknext.6

function Zip(_io, _parent, _root) { this._io = _io; this._parent = _parent; this._root = _root || this; this._read(); } Zip.prototype._read = function() { this.sections = []; var i = 0; while (!this._io.isEof()) { this.sections.push(new PkSection(this._io, this, this._root)); i++; } }

What I like best about pdf files is that I can just give them to someone and be almost certain that any questions will be about the content rather than the format of the file.

There are project layouts that put implementation files and test files together.

● Relocatable object file (.o file)○ Code and data that can be combined with other relocatable object files to form executable object file■ Each .o file is produced from exactly one source (.c) file● Executable object file (a.out file)○ Code and data that can be copied directly into memory and then executed● Shared object file (.so file)○ Special type of relocatable object file that can be loaded into memory and linked dynamically, at either load time or run-time

The NFS version 3 protocol is designed to allow servers to be as simple and general as possible. Sometimes the simplicity of the server can be a problem, if the client implements complicated file system semantics. For example, some operating systems allow removal of open files. A process can open a file and, while it is open, remove it from the directory. The file can be read and Callaghan, el al Informational [Page 96] RFC 1813 NFS Version 3 Protocol June 1995 written as long as the process keeps it open, even though the file has no name in the file system. It is impossible for a stateless server to implement these semantics. The client can do some tricks such as renaming the file on remove (to a hidden name), and only physically deleting it on close. The NFS version 3 protocol provides sufficient functionality to implement most file system semantics on a client.

Inside each first-level directory of a MAFF archive, the second-level directory named ^metadata^ (case-sensitive) is reserved and should not contain actual content. A file or folder named ^metadata^ (case-insensitive) should not exist inside any first-level directory.

MAFF files are standard ZIP files containing one or more web pages, images, or other downloadable content. Additional metadata, like the original page address, is saved along with the content.

Modern browsers that support the File System Access API (Edge and Chrome today) allow web pages to access the local file system (with your permission).

The original document file (I think - I can't test it)