# Moving, Duplicating and Deleting

The most common thing you'll do in your editor is move, duplicate and delete lines. Historically, we have done this with the use of copy/paste and the delete key when necessary. VS Code contains functionality that makes this process much more productive.&#x20;

Here are a few more keyboard shortcuts to add to your repertoire.&#x20;

| Action         | Keyboard Shortcut               |
| -------------- | ------------------------------- |
| Duplicate line | Opt/Alt + Shift + Down/Up Arrow |
| Move line      | Opt/Alt + Down/Up Arrow         |
| Delete Line    | Cmd/Ctrl + Shift + K            |

{% hint style="info" %}
Note that you don't need to select a line in VS Code to copy/cut it. Just put your cursor anywhere on the line and press Cmd/Ctrl + C or Cmd/Ctrl + X and the entire line will be cut or copied. This is the default behavior of the editor.
{% endhint %}

Open the "index.html" file in the "start" folder.

### Move the "title" tag above the "link" tag.

* Put your cursor anywhere on the "title" line
* Press **Opt/Alt + Up Arrow**

![](/files/-LlxAMqVgsJ7MVzNjQjr)

### Duplicate the "description meta tag

* Put your cursor anywhere on the line with the "meta" tag that has a name of "description"
* Press **Opt/Alt + Shift + Down Arrow**
* Change the "name" attribute to be "og:description"&#x20;

![](/files/-LlxA1G7nzaPPHQsSkYc)

### Delete the "description" meta tag

* Put your cursor anywhere on the line that has the `meta` tag with a name of "description"
* Press **Cmd/Ctrl + Shift + K**

![](/files/-Llx9X7YzcZf8ms5e2dg)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://burkeholland.gitbook.io/vs-code-can-do-that/exercise-3-navigation-and-refactoring/moving-duplicating-and-deleting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
