Skip to content
BranchesTags

Latest commit

History

104 Commits

Folders and files

NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el

Repository files navigation

org-vcard - org-mode support for vCard export and import

Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard

This project is currently unmaintained, and needs a new maintainer. If you wish to take maintainership, please email Alexis.

org-vcard is a package for exporting and importing vCards from within GNU Emacs' Org mode.

Table of Contents

Features

  • Backwards-compatible with org-contacts.el.

org-vcard comes with a built-in contacts style called flat, which adheres to org-contacts' method of structuring contacts and contact information. It not only supports the properties specified in org-contacts.el, but many other properties as well.

  • Basic support for vCard 4.0, 3.0 and 2.1.

org-vcard is working towards full compliance with the vCard 4.0 (RFC 6350), 3.0 (RFC 2426 and RFC 4770) and 2.1 specifications.

  • New contacts style: tree.

org-vcard introduces a new style for Org contacts, called tree. More details below.

  • Highly customisable, via Emacs' customize interface.

Modify existing contact styles; change the labels used to map contact details in org-mode to various vCard properties/types, or add new ones. Create completely new contact styles by plugging in your own code to handle export and import.

Installation

Install org-vcard from MELPA, MELPA Stable, or put the org-vcard folder in your load-path and do a (require 'org-vcard).

Usage

The main user commands are org-vcard-export and org-vcard-import, which are intended to be called interactively; you can press TAB at many of the minibuffer prompts to get a list of the available options for a prompt.

Both org-vcard-export and org-vcard-import are wrappers around the org-vcard-transfer-helper function. org-vcard-transfer-helper can be used to export and import programmatically (i.e. via Emacs Lisp).

Enabling org-vcard-mode will add an "Org-vCard" menu to the menu bar, from which one can access the various export, import and customisation options.

Note! When exporting to vCard using the source buffer, narrowing is respected. If you wish to export the entire buffer without restriction, remove any narrowing in effect.

For a list of the properties available by default for each contacts style and related vCard versions, visit the "Org Vcard Styles Languages Mappings" setting in the Org Vcard customize group, or examine the value of the org-vcard-styles-languages-mappings variable.

Note! The default mappings might need to be tweaked for particular use-cases. For example, some systems create vCards with a bare TEL property, whereas others use TEL;TYPE=voice; but both are mapped to the Org PHONE property (for flat style) or phone FIELDTYPE (for tree style). In this case, the customize interface could be used to delete whichever of the two mappings is unwanted.

The value of the org-vcard-include-import-unknowns (boolean) variable specifies whether the import process should include vCard properties not listed in the mapping being used.

The value of the org-vcard-append-to-existing-import-buffer and org-vcard-append-to-existing-export-buffer (boolean) variables specify whether the import/export process should append to any existing import/export buffer. If not, a new import/export buffer is created for each import/export.

The tree contacts style

The structure of the tree contacts style is:

* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:

* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to associate fields with their data, the above hierarchy is only one way to structure contacts; equivalently, one could do:

* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO

  • Add support for one-vCard-per-file export.

  • Add support for line folding when exporting.

  • Add support for multiple instances of EMAIL property.

  • Add support for vCard PREF for style flat.

  • Add support for vCard KINDs group and org.

  • Add support for per-card version handling on import.

  • Improve compliance with each version of the vCard specification.

  • Extend test coverage.

Issues / bugs

If you discover an issue or bug in org-vcard not already noted:

please create a new issue with as much detail as possible, including:

  • which version of Emacs you're running on which operating system, and

  • how you installed org-vcard.

Testing

A basic test suite is located in the repository tests directory, in org-vcard-tests.el. To run the suite:

  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).

License

GNU General Public License version 3, or (at your option) any later version.

Converted from org-vcard.el by el2markdown.

About

Export and import vCards from within GNU Emacs' Org mode.

Resources

Readme
Activity

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - Axler1/org-vcard: Export and import vCards from within GNU Emacs' Org mode. · GitHub
Skip to content
BranchesTags
Latest commit
History
104 Commits
Folders and files
NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el
Repository files navigation
org-vcard - org-mode support for vCard export and import
Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard
This project is currently unmaintained, and needs a new
maintainer. If you wish to take maintainership, please email
Alexis.
org-vcard is a package for exporting and importing
vCards from within GNU
Emacs' Org
mode.
Table of Contents
Features
  • Backwards-compatible with org-contacts.el.
org-vcard comes with a built-in contacts style called flat,
which adheres to org-contacts' method of structuring contacts and
contact information. It not only supports the properties specified
in org-contacts.el, but many other properties as well.
  • Basic support for vCard 4.0, 3.0 and 2.1.
org-vcard is working towards full compliance with the vCard 4.0
(RFC 6350), 3.0 (RFC
2426 and RFC
4770) and
2.1
specifications.
  • New contacts style: tree.
org-vcard introduces a new style for Org contacts, called
tree. More details below.
  • Highly customisable, via Emacs' customize interface.
Modify existing contact styles; change the labels used to map
contact details in org-mode to various vCard properties/types, or
add new ones. Create completely new contact styles by plugging in
your own code to handle export and import.
Installation
Install org-vcard from MELPA,
MELPA Stable, or put the
org-vcard folder in your load-path and do a (require 'org-vcard).
Usage
The main user commands are org-vcard-export and
org-vcard-import, which are intended to be called interactively;
you can press TAB at many of the minibuffer prompts to get a list
of the available options for a prompt.
Both org-vcard-export and org-vcard-import are wrappers around
the org-vcard-transfer-helper
function. org-vcard-transfer-helper can be used to export and
import programmatically (i.e. via Emacs Lisp).
Enabling org-vcard-mode will add an "Org-vCard" menu to the menu
bar, from which one can access the various export, import and
customisation options.
Note! When exporting to vCard using the source buffer,
narrowing is respected. If you wish to export the entire buffer
without restriction, remove any narrowing in effect.
For a list of the properties available by default for each contacts
style and related vCard versions, visit the "Org Vcard Styles
Languages Mappings" setting in the Org Vcard customize group, or
examine the value of the org-vcard-styles-languages-mappings
variable.
Note! The default mappings might need to be tweaked for
particular use-cases. For example, some systems create vCards
with a bare TEL property, whereas others use TEL;TYPE=voice;
but both are mapped to the Org PHONE property (for flat
style) or phone FIELDTYPE (for tree style). In this case, the
customize interface could be used to delete whichever of the
two mappings is unwanted.
The value of the org-vcard-include-import-unknowns (boolean)
variable specifies whether the import process should include vCard
properties not listed in the mapping being used.
The value of the org-vcard-append-to-existing-import-buffer and
org-vcard-append-to-existing-export-buffer (boolean) variables
specify whether the import/export process should append to any
existing import/export buffer. If not, a new import/export buffer
is created for each import/export.
The tree contacts style
The structure of the tree contacts style is:
* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:
* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to
associate fields with their data, the above hierarchy is only one
way to structure contacts; equivalently, one could do:
* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO
  • Add support for one-vCard-per-file export.
  • Add support for line folding when exporting.
  • Add support for multiple instances of EMAIL property.
  • Add support for vCard PREF for style flat.
  • Add support for vCard KINDs group and org.
  • Add support for per-card version handling on import.
  • Improve compliance with each version of the vCard specification.
  • Extend test coverage.
Issues / bugs
If you discover an issue or bug in org-vcard not already noted:
please create a new issue with as much detail as possible, including:
  • which version of Emacs you're running on which operating system, and
  • how you installed org-vcard.
Testing
A basic test suite is located in the repository tests directory,
in org-vcard-tests.el. To run the suite:
  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).
License
GNU General Public License version
3, or (at your option) any
later version.
Converted from org-vcard.el by el2markdown.
About
Export and import vCards from within GNU Emacs' Org mode.
Resources
Readme
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - Axler1/org-vcard: Export and import vCards from within GNU Emacs' Org mode. · GitHub
Skip to content
BranchesTags
Latest commit
History
104 Commits
Folders and files
NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el
Repository files navigation
org-vcard - org-mode support for vCard export and import
Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard
This project is currently unmaintained, and needs a new
maintainer. If you wish to take maintainership, please email
Alexis.
org-vcard is a package for exporting and importing
vCards from within GNU
Emacs' Org
mode.
Table of Contents
Features
  • Backwards-compatible with org-contacts.el.
org-vcard comes with a built-in contacts style called flat,
which adheres to org-contacts' method of structuring contacts and
contact information. It not only supports the properties specified
in org-contacts.el, but many other properties as well.
  • Basic support for vCard 4.0, 3.0 and 2.1.
org-vcard is working towards full compliance with the vCard 4.0
(RFC 6350), 3.0 (RFC
2426 and RFC
4770) and
2.1
specifications.
  • New contacts style: tree.
org-vcard introduces a new style for Org contacts, called
tree. More details below.
  • Highly customisable, via Emacs' customize interface.
Modify existing contact styles; change the labels used to map
contact details in org-mode to various vCard properties/types, or
add new ones. Create completely new contact styles by plugging in
your own code to handle export and import.
Installation
Install org-vcard from MELPA,
MELPA Stable, or put the
org-vcard folder in your load-path and do a (require 'org-vcard).
Usage
The main user commands are org-vcard-export and
org-vcard-import, which are intended to be called interactively;
you can press TAB at many of the minibuffer prompts to get a list
of the available options for a prompt.
Both org-vcard-export and org-vcard-import are wrappers around
the org-vcard-transfer-helper
function. org-vcard-transfer-helper can be used to export and
import programmatically (i.e. via Emacs Lisp).
Enabling org-vcard-mode will add an "Org-vCard" menu to the menu
bar, from which one can access the various export, import and
customisation options.
Note! When exporting to vCard using the source buffer,
narrowing is respected. If you wish to export the entire buffer
without restriction, remove any narrowing in effect.
For a list of the properties available by default for each contacts
style and related vCard versions, visit the "Org Vcard Styles
Languages Mappings" setting in the Org Vcard customize group, or
examine the value of the org-vcard-styles-languages-mappings
variable.
Note! The default mappings might need to be tweaked for
particular use-cases. For example, some systems create vCards
with a bare TEL property, whereas others use TEL;TYPE=voice;
but both are mapped to the Org PHONE property (for flat
style) or phone FIELDTYPE (for tree style). In this case, the
customize interface could be used to delete whichever of the
two mappings is unwanted.
The value of the org-vcard-include-import-unknowns (boolean)
variable specifies whether the import process should include vCard
properties not listed in the mapping being used.
The value of the org-vcard-append-to-existing-import-buffer and
org-vcard-append-to-existing-export-buffer (boolean) variables
specify whether the import/export process should append to any
existing import/export buffer. If not, a new import/export buffer
is created for each import/export.
The tree contacts style
The structure of the tree contacts style is:
* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:
* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to
associate fields with their data, the above hierarchy is only one
way to structure contacts; equivalently, one could do:
* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO
  • Add support for one-vCard-per-file export.
  • Add support for line folding when exporting.
  • Add support for multiple instances of EMAIL property.
  • Add support for vCard PREF for style flat.
  • Add support for vCard KINDs group and org.
  • Add support for per-card version handling on import.
  • Improve compliance with each version of the vCard specification.
  • Extend test coverage.
Issues / bugs
If you discover an issue or bug in org-vcard not already noted:
please create a new issue with as much detail as possible, including:
  • which version of Emacs you're running on which operating system, and
  • how you installed org-vcard.
Testing
A basic test suite is located in the repository tests directory,
in org-vcard-tests.el. To run the suite:
  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).
License
GNU General Public License version
3, or (at your option) any
later version.
Converted from org-vcard.el by el2markdown.
About
Export and import vCards from within GNU Emacs' Org mode.
Resources
Readme
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - Axler1/org-vcard: Export and import vCards from within GNU Emacs' Org mode. · GitHub
Skip to content
BranchesTags
Latest commit
History
104 Commits
Folders and files
NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el
Repository files navigation
org-vcard - org-mode support for vCard export and import
Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard
This project is currently unmaintained, and needs a new
maintainer. If you wish to take maintainership, please email
Alexis.
org-vcard is a package for exporting and importing
vCards from within GNU
Emacs' Org
mode.
Table of Contents
Features
  • Backwards-compatible with org-contacts.el.
org-vcard comes with a built-in contacts style called flat,
which adheres to org-contacts' method of structuring contacts and
contact information. It not only supports the properties specified
in org-contacts.el, but many other properties as well.
  • Basic support for vCard 4.0, 3.0 and 2.1.
org-vcard is working towards full compliance with the vCard 4.0
(RFC 6350), 3.0 (RFC
2426 and RFC
4770) and
2.1
specifications.
  • New contacts style: tree.
org-vcard introduces a new style for Org contacts, called
tree. More details below.
  • Highly customisable, via Emacs' customize interface.
Modify existing contact styles; change the labels used to map
contact details in org-mode to various vCard properties/types, or
add new ones. Create completely new contact styles by plugging in
your own code to handle export and import.
Installation
Install org-vcard from MELPA,
MELPA Stable, or put the
org-vcard folder in your load-path and do a (require 'org-vcard).
Usage
The main user commands are org-vcard-export and
org-vcard-import, which are intended to be called interactively;
you can press TAB at many of the minibuffer prompts to get a list
of the available options for a prompt.
Both org-vcard-export and org-vcard-import are wrappers around
the org-vcard-transfer-helper
function. org-vcard-transfer-helper can be used to export and
import programmatically (i.e. via Emacs Lisp).
Enabling org-vcard-mode will add an "Org-vCard" menu to the menu
bar, from which one can access the various export, import and
customisation options.
Note! When exporting to vCard using the source buffer,
narrowing is respected. If you wish to export the entire buffer
without restriction, remove any narrowing in effect.
For a list of the properties available by default for each contacts
style and related vCard versions, visit the "Org Vcard Styles
Languages Mappings" setting in the Org Vcard customize group, or
examine the value of the org-vcard-styles-languages-mappings
variable.
Note! The default mappings might need to be tweaked for
particular use-cases. For example, some systems create vCards
with a bare TEL property, whereas others use TEL;TYPE=voice;
but both are mapped to the Org PHONE property (for flat
style) or phone FIELDTYPE (for tree style). In this case, the
customize interface could be used to delete whichever of the
two mappings is unwanted.
The value of the org-vcard-include-import-unknowns (boolean)
variable specifies whether the import process should include vCard
properties not listed in the mapping being used.
The value of the org-vcard-append-to-existing-import-buffer and
org-vcard-append-to-existing-export-buffer (boolean) variables
specify whether the import/export process should append to any
existing import/export buffer. If not, a new import/export buffer
is created for each import/export.
The tree contacts style
The structure of the tree contacts style is:
* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:
* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to
associate fields with their data, the above hierarchy is only one
way to structure contacts; equivalently, one could do:
* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO
  • Add support for one-vCard-per-file export.
  • Add support for line folding when exporting.
  • Add support for multiple instances of EMAIL property.
  • Add support for vCard PREF for style flat.
  • Add support for vCard KINDs group and org.
  • Add support for per-card version handling on import.
  • Improve compliance with each version of the vCard specification.
  • Extend test coverage.
Issues / bugs
If you discover an issue or bug in org-vcard not already noted:
please create a new issue with as much detail as possible, including:
  • which version of Emacs you're running on which operating system, and
  • how you installed org-vcard.
Testing
A basic test suite is located in the repository tests directory,
in org-vcard-tests.el. To run the suite:
  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).
License
GNU General Public License version
3, or (at your option) any
later version.
Converted from org-vcard.el by el2markdown.
About
Export and import vCards from within GNU Emacs' Org mode.
Resources
Readme
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - Axler1/org-vcard: Export and import vCards from within GNU Emacs' Org mode. · GitHub
Skip to content
BranchesTags
Latest commit
History
104 Commits
Folders and files
NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el
Repository files navigation
org-vcard - org-mode support for vCard export and import
Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard
This project is currently unmaintained, and needs a new
maintainer. If you wish to take maintainership, please email
Alexis.
org-vcard is a package for exporting and importing
vCards from within GNU
Emacs' Org
mode.
Table of Contents
Features
  • Backwards-compatible with org-contacts.el.
org-vcard comes with a built-in contacts style called flat,
which adheres to org-contacts' method of structuring contacts and
contact information. It not only supports the properties specified
in org-contacts.el, but many other properties as well.
  • Basic support for vCard 4.0, 3.0 and 2.1.
org-vcard is working towards full compliance with the vCard 4.0
(RFC 6350), 3.0 (RFC
2426 and RFC
4770) and
2.1
specifications.
  • New contacts style: tree.
org-vcard introduces a new style for Org contacts, called
tree. More details below.
  • Highly customisable, via Emacs' customize interface.
Modify existing contact styles; change the labels used to map
contact details in org-mode to various vCard properties/types, or
add new ones. Create completely new contact styles by plugging in
your own code to handle export and import.
Installation
Install org-vcard from MELPA,
MELPA Stable, or put the
org-vcard folder in your load-path and do a (require 'org-vcard).
Usage
The main user commands are org-vcard-export and
org-vcard-import, which are intended to be called interactively;
you can press TAB at many of the minibuffer prompts to get a list
of the available options for a prompt.
Both org-vcard-export and org-vcard-import are wrappers around
the org-vcard-transfer-helper
function. org-vcard-transfer-helper can be used to export and
import programmatically (i.e. via Emacs Lisp).
Enabling org-vcard-mode will add an "Org-vCard" menu to the menu
bar, from which one can access the various export, import and
customisation options.
Note! When exporting to vCard using the source buffer,
narrowing is respected. If you wish to export the entire buffer
without restriction, remove any narrowing in effect.
For a list of the properties available by default for each contacts
style and related vCard versions, visit the "Org Vcard Styles
Languages Mappings" setting in the Org Vcard customize group, or
examine the value of the org-vcard-styles-languages-mappings
variable.
Note! The default mappings might need to be tweaked for
particular use-cases. For example, some systems create vCards
with a bare TEL property, whereas others use TEL;TYPE=voice;
but both are mapped to the Org PHONE property (for flat
style) or phone FIELDTYPE (for tree style). In this case, the
customize interface could be used to delete whichever of the
two mappings is unwanted.
The value of the org-vcard-include-import-unknowns (boolean)
variable specifies whether the import process should include vCard
properties not listed in the mapping being used.
The value of the org-vcard-append-to-existing-import-buffer and
org-vcard-append-to-existing-export-buffer (boolean) variables
specify whether the import/export process should append to any
existing import/export buffer. If not, a new import/export buffer
is created for each import/export.
The tree contacts style
The structure of the tree contacts style is:
* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:
* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to
associate fields with their data, the above hierarchy is only one
way to structure contacts; equivalently, one could do:
* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO
  • Add support for one-vCard-per-file export.
  • Add support for line folding when exporting.
  • Add support for multiple instances of EMAIL property.
  • Add support for vCard PREF for style flat.
  • Add support for vCard KINDs group and org.
  • Add support for per-card version handling on import.
  • Improve compliance with each version of the vCard specification.
  • Extend test coverage.
Issues / bugs
If you discover an issue or bug in org-vcard not already noted:
please create a new issue with as much detail as possible, including:
  • which version of Emacs you're running on which operating system, and
  • how you installed org-vcard.
Testing
A basic test suite is located in the repository tests directory,
in org-vcard-tests.el. To run the suite:
  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).
License
GNU General Public License version
3, or (at your option) any
later version.
Converted from org-vcard.el by el2markdown.
About
Export and import vCards from within GNU Emacs' Org mode.
Resources
Readme
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - Axler1/org-vcard: Export and import vCards from within GNU Emacs' Org mode. · GitHub
Skip to content
BranchesTags
Latest commit
History
104 Commits
Folders and files
NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el
Repository files navigation
org-vcard - org-mode support for vCard export and import
Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard
This project is currently unmaintained, and needs a new
maintainer. If you wish to take maintainership, please email
Alexis.
org-vcard is a package for exporting and importing
vCards from within GNU
Emacs' Org
mode.
Table of Contents
Features
  • Backwards-compatible with org-contacts.el.
org-vcard comes with a built-in contacts style called flat,
which adheres to org-contacts' method of structuring contacts and
contact information. It not only supports the properties specified
in org-contacts.el, but many other properties as well.
  • Basic support for vCard 4.0, 3.0 and 2.1.
org-vcard is working towards full compliance with the vCard 4.0
(RFC 6350), 3.0 (RFC
2426 and RFC
4770) and
2.1
specifications.
  • New contacts style: tree.
org-vcard introduces a new style for Org contacts, called
tree. More details below.
  • Highly customisable, via Emacs' customize interface.
Modify existing contact styles; change the labels used to map
contact details in org-mode to various vCard properties/types, or
add new ones. Create completely new contact styles by plugging in
your own code to handle export and import.
Installation
Install org-vcard from MELPA,
MELPA Stable, or put the
org-vcard folder in your load-path and do a (require 'org-vcard).
Usage
The main user commands are org-vcard-export and
org-vcard-import, which are intended to be called interactively;
you can press TAB at many of the minibuffer prompts to get a list
of the available options for a prompt.
Both org-vcard-export and org-vcard-import are wrappers around
the org-vcard-transfer-helper
function. org-vcard-transfer-helper can be used to export and
import programmatically (i.e. via Emacs Lisp).
Enabling org-vcard-mode will add an "Org-vCard" menu to the menu
bar, from which one can access the various export, import and
customisation options.
Note! When exporting to vCard using the source buffer,
narrowing is respected. If you wish to export the entire buffer
without restriction, remove any narrowing in effect.
For a list of the properties available by default for each contacts
style and related vCard versions, visit the "Org Vcard Styles
Languages Mappings" setting in the Org Vcard customize group, or
examine the value of the org-vcard-styles-languages-mappings
variable.
Note! The default mappings might need to be tweaked for
particular use-cases. For example, some systems create vCards
with a bare TEL property, whereas others use TEL;TYPE=voice;
but both are mapped to the Org PHONE property (for flat
style) or phone FIELDTYPE (for tree style). In this case, the
customize interface could be used to delete whichever of the
two mappings is unwanted.
The value of the org-vcard-include-import-unknowns (boolean)
variable specifies whether the import process should include vCard
properties not listed in the mapping being used.
The value of the org-vcard-append-to-existing-import-buffer and
org-vcard-append-to-existing-export-buffer (boolean) variables
specify whether the import/export process should append to any
existing import/export buffer. If not, a new import/export buffer
is created for each import/export.
The tree contacts style
The structure of the tree contacts style is:
* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:
* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to
associate fields with their data, the above hierarchy is only one
way to structure contacts; equivalently, one could do:
* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO
  • Add support for one-vCard-per-file export.
  • Add support for line folding when exporting.
  • Add support for multiple instances of EMAIL property.
  • Add support for vCard PREF for style flat.
  • Add support for vCard KINDs group and org.
  • Add support for per-card version handling on import.
  • Improve compliance with each version of the vCard specification.
  • Extend test coverage.
Issues / bugs
If you discover an issue or bug in org-vcard not already noted:
please create a new issue with as much detail as possible, including:
  • which version of Emacs you're running on which operating system, and
  • how you installed org-vcard.
Testing
A basic test suite is located in the repository tests directory,
in org-vcard-tests.el. To run the suite:
  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).
License
GNU General Public License version
3, or (at your option) any
later version.
Converted from org-vcard.el by el2markdown.
About
Export and import vCards from within GNU Emacs' Org mode.
Resources
Readme
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - Axler1/org-vcard: Export and import vCards from within GNU Emacs' Org mode. · GitHub
Skip to content
BranchesTags
Latest commit
History
104 Commits
Folders and files
NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el
Repository files navigation
org-vcard - org-mode support for vCard export and import
Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard
This project is currently unmaintained, and needs a new
maintainer. If you wish to take maintainership, please email
Alexis.
org-vcard is a package for exporting and importing
vCards from within GNU
Emacs' Org
mode.
Table of Contents
Features
  • Backwards-compatible with org-contacts.el.
org-vcard comes with a built-in contacts style called flat,
which adheres to org-contacts' method of structuring contacts and
contact information. It not only supports the properties specified
in org-contacts.el, but many other properties as well.
  • Basic support for vCard 4.0, 3.0 and 2.1.
org-vcard is working towards full compliance with the vCard 4.0
(RFC 6350), 3.0 (RFC
2426 and RFC
4770) and
2.1
specifications.
  • New contacts style: tree.
org-vcard introduces a new style for Org contacts, called
tree. More details below.
  • Highly customisable, via Emacs' customize interface.
Modify existing contact styles; change the labels used to map
contact details in org-mode to various vCard properties/types, or
add new ones. Create completely new contact styles by plugging in
your own code to handle export and import.
Installation
Install org-vcard from MELPA,
MELPA Stable, or put the
org-vcard folder in your load-path and do a (require 'org-vcard).
Usage
The main user commands are org-vcard-export and
org-vcard-import, which are intended to be called interactively;
you can press TAB at many of the minibuffer prompts to get a list
of the available options for a prompt.
Both org-vcard-export and org-vcard-import are wrappers around
the org-vcard-transfer-helper
function. org-vcard-transfer-helper can be used to export and
import programmatically (i.e. via Emacs Lisp).
Enabling org-vcard-mode will add an "Org-vCard" menu to the menu
bar, from which one can access the various export, import and
customisation options.
Note! When exporting to vCard using the source buffer,
narrowing is respected. If you wish to export the entire buffer
without restriction, remove any narrowing in effect.
For a list of the properties available by default for each contacts
style and related vCard versions, visit the "Org Vcard Styles
Languages Mappings" setting in the Org Vcard customize group, or
examine the value of the org-vcard-styles-languages-mappings
variable.
Note! The default mappings might need to be tweaked for
particular use-cases. For example, some systems create vCards
with a bare TEL property, whereas others use TEL;TYPE=voice;
but both are mapped to the Org PHONE property (for flat
style) or phone FIELDTYPE (for tree style). In this case, the
customize interface could be used to delete whichever of the
two mappings is unwanted.
The value of the org-vcard-include-import-unknowns (boolean)
variable specifies whether the import process should include vCard
properties not listed in the mapping being used.
The value of the org-vcard-append-to-existing-import-buffer and
org-vcard-append-to-existing-export-buffer (boolean) variables
specify whether the import/export process should append to any
existing import/export buffer. If not, a new import/export buffer
is created for each import/export.
The tree contacts style
The structure of the tree contacts style is:
* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:
* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to
associate fields with their data, the above hierarchy is only one
way to structure contacts; equivalently, one could do:
* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO
  • Add support for one-vCard-per-file export.
  • Add support for line folding when exporting.
  • Add support for multiple instances of EMAIL property.
  • Add support for vCard PREF for style flat.
  • Add support for vCard KINDs group and org.
  • Add support for per-card version handling on import.
  • Improve compliance with each version of the vCard specification.
  • Extend test coverage.
Issues / bugs
If you discover an issue or bug in org-vcard not already noted:
please create a new issue with as much detail as possible, including:
  • which version of Emacs you're running on which operating system, and
  • how you installed org-vcard.
Testing
A basic test suite is located in the repository tests directory,
in org-vcard-tests.el. To run the suite:
  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).
License
GNU General Public License version
3, or (at your option) any
later version.
Converted from org-vcard.el by el2markdown.
About
Export and import vCards from within GNU Emacs' Org mode.
Resources
Readme
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
GitHub - Axler1/org-vcard: Export and import vCards from within GNU Emacs' Org mode. · GitHub
Skip to content
BranchesTags
Latest commit
History
104 Commits
Folders and files
NameName
Last commit message
Last commit date
styles
styles
tests
tests
README.md
README.md
org-vcard.el
org-vcard.el
Repository files navigation
org-vcard - org-mode support for vCard export and import
Author: Alexis flexibeast@gmail.com, Will Dey will123dey@gmail.com
URL:https://github.com/flexibeast/org-vcard
This project is currently unmaintained, and needs a new
maintainer. If you wish to take maintainership, please email
Alexis.
org-vcard is a package for exporting and importing
vCards from within GNU
Emacs' Org
mode.
Table of Contents
Features
  • Backwards-compatible with org-contacts.el.
org-vcard comes with a built-in contacts style called flat,
which adheres to org-contacts' method of structuring contacts and
contact information. It not only supports the properties specified
in org-contacts.el, but many other properties as well.
  • Basic support for vCard 4.0, 3.0 and 2.1.
org-vcard is working towards full compliance with the vCard 4.0
(RFC 6350), 3.0 (RFC
2426 and RFC
4770) and
2.1
specifications.
  • New contacts style: tree.
org-vcard introduces a new style for Org contacts, called
tree. More details below.
  • Highly customisable, via Emacs' customize interface.
Modify existing contact styles; change the labels used to map
contact details in org-mode to various vCard properties/types, or
add new ones. Create completely new contact styles by plugging in
your own code to handle export and import.
Installation
Install org-vcard from MELPA,
MELPA Stable, or put the
org-vcard folder in your load-path and do a (require 'org-vcard).
Usage
The main user commands are org-vcard-export and
org-vcard-import, which are intended to be called interactively;
you can press TAB at many of the minibuffer prompts to get a list
of the available options for a prompt.
Both org-vcard-export and org-vcard-import are wrappers around
the org-vcard-transfer-helper
function. org-vcard-transfer-helper can be used to export and
import programmatically (i.e. via Emacs Lisp).
Enabling org-vcard-mode will add an "Org-vCard" menu to the menu
bar, from which one can access the various export, import and
customisation options.
Note! When exporting to vCard using the source buffer,
narrowing is respected. If you wish to export the entire buffer
without restriction, remove any narrowing in effect.
For a list of the properties available by default for each contacts
style and related vCard versions, visit the "Org Vcard Styles
Languages Mappings" setting in the Org Vcard customize group, or
examine the value of the org-vcard-styles-languages-mappings
variable.
Note! The default mappings might need to be tweaked for
particular use-cases. For example, some systems create vCards
with a bare TEL property, whereas others use TEL;TYPE=voice;
but both are mapped to the Org PHONE property (for flat
style) or phone FIELDTYPE (for tree style). In this case, the
customize interface could be used to delete whichever of the
two mappings is unwanted.
The value of the org-vcard-include-import-unknowns (boolean)
variable specifies whether the import process should include vCard
properties not listed in the mapping being used.
The value of the org-vcard-append-to-existing-import-buffer and
org-vcard-append-to-existing-export-buffer (boolean) variables
specify whether the import/export process should append to any
existing import/export buffer. If not, a new import/export buffer
is created for each import/export.
The tree contacts style
The structure of the tree contacts style is:
* [Contact name]
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** [Information type]
*** [Information value]
:PROPERTIES:
:FIELDTYPE: [Field type]
[:PREFERRED:]
:END:

Here's an example:
* Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
** Mobile
*** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
** Email
*** Work
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
*** Home
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

As the tree style uses a heading's FIELDTYPE property to
associate fields with their data, the above hierarchy is only one
way to structure contacts; equivalently, one could do:
* People
** Joan Smith
:PROPERTIES:
:KIND: individual
:FIELDTYPE: name
:END:
*** Cell
**** 0000 999 999
:PROPERTIES:
:FIELDTYPE: cell
:END:
*** Email
**** address1@hidden
:PROPERTIES:
:FIELDTYPE: email-work
:PREFERRED:
:END:
**** address2@hidden
:PROPERTIES:
:FIELDTYPE: email-home
:END:

TODO
  • Add support for one-vCard-per-file export.
  • Add support for line folding when exporting.
  • Add support for multiple instances of EMAIL property.
  • Add support for vCard PREF for style flat.
  • Add support for vCard KINDs group and org.
  • Add support for per-card version handling on import.
  • Improve compliance with each version of the vCard specification.
  • Extend test coverage.
Issues / bugs
If you discover an issue or bug in org-vcard not already noted:
please create a new issue with as much detail as possible, including:
  • which version of Emacs you're running on which operating system, and
  • how you installed org-vcard.
Testing
A basic test suite is located in the repository tests directory,
in org-vcard-tests.el. To run the suite:
  1. Ensure org-vcard.el has been loaded, e.g. (load "~/org-vcard/org-vcard.el").
  2. Load the test suite: e.g. (load "~/org-vcard/tests/org-vcard-tests.el").
  3. Run the tests by evaluating (ert '(tag org-vcard)).
License
GNU General Public License version
3, or (at your option) any
later version.
Converted from org-vcard.el by el2markdown.
About
Export and import vCards from within GNU Emacs' Org mode.
Resources
Readme
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages