100 lines
No EOL
3.8 KiB
JSON
100 lines
No EOL
3.8 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "f5e9fc34-5eff-4b6a-a2d6-f352d2728b38"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-16T14:13:04+00:00"
|
|
}
|
|
],
|
|
"revision_uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"revision_log": [],
|
|
"status": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"title": [
|
|
{
|
|
"value": "Why I use tmux\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-04-08T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:13:04+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2023\/04\/08\/why-i-use-tmux",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>tmux is a \"terminal multiplexer\" - a program that makes one terminal window into many.<\/p>\n\n<p>I use the terminal a lot and am often switching between codebase so this is very useful for me.<\/p>\n\n<p>I use a different session for each codebase. If I'm working on one and need to switch to another, I can detatch from one session and attach to another. Later, when I'm ready to switch back, I do the same again.<\/p>\n\n<p>I usually have multiple windows inside a session. Neovim will be in the main one, and I can run separate commands - especially long-running ones like watchers - with their own windows.<\/p>\n\n<p>If I need to split a window and have Neovim on the left and a terminal for running tests on the right, I can do this with different panes.<\/p>\n\n<p>Being able to organise my workspace in this way has become a big part blogof my development workflow and my productivity.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>tmux is a \"terminal multiplexer\" - a program that makes one terminal window into many.<\/p>\n\n<p>I use the terminal a lot and am often switching between codebase so this is very useful for me.<\/p>\n\n<p>I use a different session for each codebase. If I'm working on one and need to switch to another, I can detatch from one session and attach to another. Later, when I'm ready to switch back, I do the same again.<\/p>\n\n<p>I usually have multiple windows inside a session. Neovim will be in the main one, and I can run separate commands - especially long-running ones like watchers - with their own windows.<\/p>\n\n<p>If I need to split a window and have Neovim on the left and a terminal for running tests on the right, I can do this with different panes.<\/p>\n\n<p>Being able to organise my workspace in this way has become a big part blogof my development workflow and my productivity.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:13:04+00:00",
|
|
"guid": null,
|
|
"hash": "b46a6b2e5b2994af854133e567634c6c",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |